What problem does it solve?
Bug reports are often vague, intermittent, environment-specific, or mixed with an assumed cause, leading developers to fix the wrong thing or destroy evidence while investigating. This Skill enforces a disciplined workflow that proves the smallest observable failure before any diagnosis or repair begins.
Core Features & Use Cases
- Structured Evidence Capture: Records the exact error, environment facts (commit, runtime versions, lockfile, feature flags), and separates expected from actual behavior without embedding suspected causes.
- Minimal Reproduction Reduction: Systematically removes unrelated data, services, and steps until only the smallest failing fixture remains, then proves repeatability by running it multiple times.
- Safety Boundaries: Prohibits editing implementation code during reproduction, changing production data, or exposing secrets, keeping diagnosis separate from remediation.
- Use Case: A QA engineer reports that checkout fails intermittently on staging. Use this Skill to reduce the failure to a minimal test fixture, document the exact commands and outputs, and hand a verified reproduction brief to the developer.
Quick Start
Use the Bug Reproduction Brief skill on the failing checkout test, reduce it to the smallest safe failing fixture, and report the exact command evidence, expected result, actual result, and remaining unknowns without fixing it.
