What problem does it solve? Writing consistent, actionable bug reports is tedious, and teams often file reports missing reproduction steps, severity ratings, or environment context, making bugs hard to triage and fix. ## Core Features & Use Cases - Structured Report Generation: Converts a plain-language bug description into a complete report with severity, priority, environment, reproduction steps, and technical context. - Code Analysis Mode: Scans target files to detect potential bugs such as null references, off-by-one errors, race conditions, and resource leaks, then drafts a report for each finding. - Verify and Close Lifecycle: Re-runs reproduction steps and related tests to confirm a fix works, then writes a closure record so bugs are never closed without verification. - Use Case: A QA tester describes a crash that happens when opening the inventory screen; the Skill searches the codebase for related files, drafts a full report with reproduction steps, and saves it to production/qa/bugs/ for triage. ## Quick Start Use the bug-report skill to create a structured bug report for the crash that occurs when opening the inventory screen.