Bisect the Regression

SkillDev tools

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Bisect the Regression skill

What this skill tells your AI

The instructions your AI receives, as published by archive228/loopkit in skills/bisect-regression/SKILL.md and read by ahel’s review.

Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
git bisect start; git bisect bad <bad>; git bisect good <good>.
At each step, run the SMALLEST test that distinguishes good from bad. Mark git bisect good/bad.
When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
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.

Advanced