Debug and Minimize a Bug

Turn a bug report into a verified minimal reproduction, a root cause, and a fix. The prompt in references/bug-minimizer.md is the method and the output format; this file says how to fill it and when to stop.

Also invoked as /write:bug-minimizer (that skill was merged into this one).

Workflow

1. Read the prompt

Read references/bug-minimizer.md. Its fields are [BRACKET] placeholders with no defaults.

2. Intake: fill the fields from the report

Pre-fill every [BRACKET] field from the report, the code, and the repo (language from file extensions, versions from python3 --version, node --version, lockfiles, uname -sr). Use n/a for fields that do not apply (a stdlib script has no framework; a CLI has no browser) and unknown for facts nobody has given. Never ship a delivered analysis with a raw [BRACKET] left in it.

Two fields are required before any analysis: how to trigger it (a command, steps, or code) and what actually happens (output, error, or observed behavior). If either is missing: