Acm Bug Fix Verifier | Agent Skills Atlas

About this skill

Verifies whether a known ACM bug fix has landed on a target environment. Takes a JIRA ticket and a cluster, runs a 7-phase pipeline: parallel JIRA/PR/environment investigation, three-tier fix presence check (branch reachability, build date, code presence), PR code review for fix correctness, Neo4j prerequisite gap analysis with heuristic fallback, Playwright-driven UI/API verification, and verdict with optional JIRA update. Produces BLOCKED, NOTFIXED, PRESENT, or VERIFIED verdicts with evidence trail. TRIGGER: verify bug fix, confirm fix landed, check if fixed, is the bug fixed, verify ACM-NNNNN on cluster, test fix on environment. DO NOT TRIGGER: hunt for new bugs (use acm-bug-hunter), write test cases (use acm-test-case-generator), cluster health check (use acm-hub-health-check), PR-only code review (use acm-qe-code-analyzer).

Quick start

Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.

Installation guide →

Review, license & listing details

Review the source before using this skill

This is an imported listing. We haven’t certified its safety, license, or compatibility. Skills may include executable scripts.

Automated security scan: Unavailable

HTTP 404

About scan coverage and limitations

Original listing metadata

Original name

acm-bug-fix-verifier

Original description

Verifies whether a known ACM bug fix has landed on a target environment. Takes a JIRA ticket and a cluster, runs a 7-phase pipeline: parallel JIRA/PR/environment investigation, three-tier fix presence check (branch reachability, build date, code presence), PR code review for fix correctness, Neo4j prerequisite gap analysis with heuristic fallback, Playwright-driven UI/API verification, and verdict with optional JIRA update. Produces BLOCKED, NOT_FIXED, PRESENT, or VERIFIED verdicts with evidence trail. TRIGGER: verify bug fix, confirm fix landed, check if fixed, is the bug fixed, verify ACM-NNNNN on cluster, test fix on environment. DO NOT TRIGGER: hunt for new bugs (use acm-bug-hunter), write test cases (use acm-test-case-generator), cluster health check (use acm-hub-health-check), PR-only code review (use acm-qe-code-analyzer).

About this listing

Category: Developer tools
Reported license: Apache-2.0
Listing language (estimated): English
Review status: Not individually reviewed
Agent compatibility: Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.