bisect
Skill2 starsChanged 4 months agoMITView on GitHub
Find the commit that introduced a regression using git bisect, guided by a description of what broke and a way to test it. Use when the user says "find the commit that broke this", "bisect this regression", "when did this stop working", "git bisect", or "what change caused this bug".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- paultyng/skill-issuetheir own version, first seen Oct 13, 2026
- tejastn10/workbenchtheir own version, first seen Oct 13, 2026
- sirius-db/siriustheir own version, first seen Oct 8, 2026
- ClickHouse/ClickHousetheir own version, first seen Oct 8, 2026
- ohm41321/luciazerotheir own version, first seen Aug 12, 2026
- lkc-studio/claude-skill-bisecttheir own version, first seen Jul 28, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- ClickHouse/ClickHouse★ 51ksame name
- sirius-db/sirius★ 1.1ksame name
- paultyng/skill-issue★ 8same name
- ohm41321/luciazero★ 6same name
- anuq/my-claude-skills★ 1same name
- lkc-studio/claude-skill-bisect★ 1same name
- tejastn10/workbench★ 1same name
- tokyubevoxelverse/bisect★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Confirm the working tree is clean: If there are uncommitted changes, stop and tell the user to stash or commit first — bisect checks out …
- Very specific: line 29
Start: git bisect start, then git bisect bad <bad> and git bisect good <good>.
- Very specific: line 30
Prefer
git bisect run <command>: when a deterministic test command exists — it automates the whole search. - Distinctive: line 31
If the test must be manual, check out each step, have the user test, and relay git bisect good / git bisect bad per step.
- Very specific: line 32
When bisect names the first bad commit, git bisect reset to restore the original HEAD — always clean up, even if interrupted.
- Very specific: line 38
If the cause is subtle, hand off to the debug skill to drive the fix.
- Distinctive: line 42
Never run bisect with a dirty working tree.
- Distinctive: line 43
Keep the pass/fail test deterministic and fast — flaky tests give wrong answers.
- Distinctive: line 44
Don't modify code during the bisect.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo state
!git log --oneline -15 2>/dev/null || echo "Not a git repository"
!git tag --sort=-creatordate 2>/dev/null | head -10
!git status --short 2>/dev/null
Instructions
Locate the commit that introduced the regression described in $ARGUMENTS using git bisect. If the symptom or a way to reproduce it isn't clear, ask before touching the repo.
Before starting
- Confirm the working tree is clean. If there are uncommitted changes, stop and tell the user to stash or commit first — bisect checks out old commits and would clobber or be blocked by them.
- Establish a "bad" and a "good" ref. "Bad" is usually
HEAD. For "good", use the ref the user named, or help find a plausible older commit/tag where the behavior worked. Verify the assumption if cheap (e.g. note when the relevant code was last touched). - Define a precise pass/fail test. A single command that exits 0 when good and non-zero when bad is ideal (a failing test, a build, a script, a grep on output). Pin this down — a fuzzy "it looks broken" makes bisect unreliable.
Running the bisect
- Start:
git bisect start, thengit bisect bad <bad>andgit bisect good <good>. - Prefer
git bisect run <command>when a deterministic test command exists — it automates the whole search. Make sure the command's exit code reflects pass/fail (use exit code125to skip un-testable commits, e.g. ones that don't build for unrelated reasons). - If the test must be manual, check out each step, have the user test, and relay
git bisect good/git bisect badper step. - When bisect names the first bad commit,
git bisect resetto restore the originalHEAD— always clean up, even if interrupted.
After finding it
- Show the offending commit:
git show <sha> --stat, then read the actual diff to explain why it caused the regression. - Summarize: the first bad commit, what it changed, the likely mechanism of the break, and a suggested fix or revert (
git revert <sha>for a clean undo). - If the cause is subtle, hand off to the
debugskill to drive the fix.
Rules
- Never run bisect with a dirty working tree. Always
git bisect resetwhen done or on any error. - Keep the pass/fail test deterministic and fast — flaky tests give wrong answers. Use
git bisect skipfor commits that genuinely can't be tested. - Don't modify code during the bisect; this is diagnosis. Propose the fix separately once the commit is found.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

