Git bisect
Skill kimtth/agent-skill-100-lines-or-less/skills/git-bisect
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill git-bisectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: find the commit that introduced a bug with a binary search over history.
SKILL.md
1.0 KB, as published. Nobody here has run it
Goal: pinpoint the exact commit that caused a regression.
Use for:
- a bug that appeared somewhere in a range of commits
- regressions with a clear good and bad state
- narrowing blame when the diff is large
Workflow:
- Find a known-good and a known-bad commit.
- Start bisect: mark bad, then mark good.
- Test the checkout git selects at each step.
- Mark each as good or bad to halve the range.
- Let bisect converge on the first bad commit.
- Reset bisect and inspect that commit's diff.
Automate:
- write a script that exits 0 (good) or non-zero (bad)
- run git bisect run <script> to search hands-free
- ensure the test reliably reproduces the bug
Rules:
- use a reliable, fast reproducer for each step
- keep the working tree clean between steps
- run git bisect reset when finished
- a flaky test makes bisect lie; stabilize it first