What problem does it solve? After a bug fix is applied, teams often lack a structured way to confirm the fix actually resolves the original symptom without introducing regressions. This Skill closes that gap by re-running reproduction steps and test suites, then recording a formal verification report. ## Core Features & Use Cases - Fix Verification: Re-runs the reproduction steps from the bug assessment and the tests added by the fix to confirm the symptom is gone. - Regression Checking: Executes existing test suites, lint, and type-checks for the changed modules to detect side effects. - Structured Reporting: Writes a verification report to .specify/bugs/<slug>/test.md with a verdict of verified, partial, or failed, plus checks performed, output excerpts, and residual risks. - Use Case: After running a bug-fix workflow on a login timeout issue, invoke this Skill to re-execute the reproduction steps and test suite, producing an auditable report that decides whether to close, hold, or reopen the bug. ## Quick Start Validate the fix for the login-timeout bug and generate the verification report in its bug directory.
