Skill
Git Bisect Regression
Finds the exact commit that introduced a regression by running git bisect with an automated test, then explains what that commit changed.
1Find the first bad commit with a script, not by eye.
2Steps
31. Pin down the failure and the range. Ask for a known good commit or tag if the user has not named one; if they have none, probe older tags until the check passes.
42. Write the check as a command that exits 0 when the code is good, 1 when bad, and 125 when the commit cannot be tested (does not build, missing dependency). Prefer an existing failing test: `npm test -- -t "name"`, `pytest path::test`, `go test -run Name`. Otherwise a small script in a temp file outside the repository.
53. Validate the check before starting: it must fail on the bad commit and pass on the good one. A check that is flaky gives a wrong answer, so run it three times on each end.
Claude CodeCodex
Git Bisect Regression
SkillGit and releases
Free