# Bisect Regression

Find the exact commit that introduced a bug.

- Repository: https://github.com/Archive228/loopkit (756 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-07-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Archive228/loopkit --skill bisect-regression -g -a claude-code -y`
Codex: `npx skills add Archive228/loopkit --skill bisect-regression -g -a codex -y`
Cursor: `npx skills add Archive228/loopkit --skill bisect-regression -g -a cursor -y`
Gemini CLI: `npx skills add Archive228/loopkit --skill bisect-regression -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Archive228/loopkit`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.