agentsclimarketplace
Sign in

Bisect regression

Skill Archive228/loopkit/skills/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.From its SKILL.md

Install
npx -y skills add Archive228/loopkit --skill bisect-regression

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

0.8 KB, as published. Nobody here has run 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.

Keep looking

Skills are one crate of 626,474. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.