Verify Bug

Automates the full post-merge verification loop: pulls reproduce steps from JIRA, walks them in a named Playwright session across UAT markets, compares screenshots against expected results, and updates the ticket with pass/fail evidence. The diagnostic decoder is clever, it categorizes failures as VPN issues, blocked accounts, or actual regressions before you waste time investigating. Handles multi-market scope with parallel execution and credential validation upfront. If it passes, it transitions the ticket to Ready for Production and attaches wiki-formatted proof. Built for teams that treat UAT like production and need audit trails that survive compliance reviews. The hover discipline and animation masking show someone actually ran flaky UI tests before writing this.

GitHub stars: 504
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill verify-bug --agent claude-code

Installs into .claude/skills of the current project.

Files

Verify Bug Skill

[!IMPORTANT] Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Instructions

When the user asks to perform this workflow, execute the following steps:

Verify-Bug — UAT Audit

Goal: Prove a bug fix works in the UAT environment via comparative Before/After evidence, then transition ticket status.

Input

/verify-bug <jira-url-or-key> [--baseline-image <url>]

Workflow

Step 0: Pre-flight & Data Gathering

[!TIP] Sub-Agent Delegation: If your platform supports sub-agents (e.g., Claude, OpenCode, Gemini, Kiro), delegate steps 1-3 below to your JIRA Analyst sub-agent (e.g., @specialist-jira-analyst). If sub-agents are NOT supported (e.g., Antigravity, Windsurf), you must execute these steps yourself.

SKILL.md on GitHub