What problem does it solve? Writing consistent, actionable bug reports is tedious and often results in missing reproduction steps, unclear severity, or lost context. This Skill standardizes the entire bug lifecycle—from initial report through verification and closure—so every defect is documented with full technical context. ## Core Features & Use Cases - Structured Report Generation: Turns a plain-language bug description into a complete report with severity, priority, environment, reproduction steps, and likely affected files found via codebase search. - Code Analysis Mode: Scans target files to identify potential bugs such as null references, off-by-one errors, race conditions, and resource leaks, generating a report for each finding. - Verify and Close Workflow: Re-runs reproduction steps and related tests to confirm fixes, then writes closure records with resolution details and regression test references. - Use Case: A QA tester describes a crash when opening the inventory screen. The Skill searches the codebase, drafts a BUG-0042 report with reproduction steps and suspected files, saves it to production/qa/bugs/, and later verifies the fix before closing it. ## Quick Start Use the bug-report skill to create a structured bug report for the crash that happens when opening the inventory screen after loading a saved game.
