bisect-regression
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Source facts
- Repository
- Archive228/loopkit
- Last source activity
- June 29, 2026 at 21:52
- Detected SKILL.md language
- English
- Stars
- 757
- Forks
- 124
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- 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.
# Bisect the Regression
1. Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
2. `git bisect start; git bisect bad <bad>; git bisect good <good>`.
3. At each step, run the SMALLEST test that distinguishes good from bad. Mark `git bisect good/bad`.
4. When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
5. `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.
View on GitHub