Menu
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | bisect-regression |
| description | Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it. |
git bisect start; git bisect bad <bad>; git bisect good <good>.git bisect good/bad.git bisect reset. Report: the commit, the line, the one-sentence cause.
Automate it: git bisect run ./repro.sh if you have a script that exits non-zero on the bug.Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.
Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.
Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.
Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.
Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.