bisect 🎯

Describe the bug. Get the commit that caused it.

git bisect is the most powerful debugging tool nobody uses, because driving it by hand is tedious and building a reliable check is fiddly. bisect the skill does both: you describe the regression in plain English — "scrolling got janky sometime last month" — and it writes the check script, validates it against a known-good ref, drives git bisect run in an isolated worktree, and hands you the guilty commit with an explanation of why it broke and whether a revert is clean.

Install

Works as a Claude Code skill:

# available in every project
git clone https://github.com/tokyubevoxelverse/bisect ~/.claude/skills/bisect

# or just one project
git clone https://github.com/tokyubevoxelverse/bisect .claude/skills/bisect

Use

/bisect the search endpoint started returning 500s, it worked in v2.3
/bisect npm test fails on TestCheckout — find what broke it
/bisect startup time doubled sometime since March

How it works

1. Build the oracle — your symptom becomes an executable pass/fail script, validated to fail on HEAD and pass on a good ref before anything else happens. No verified pair, no bisect.
2. Drive the machine — git bisect run in a separate worktree (your working directory is never touched), with automatic skip for unbuildable commits and per-era dependency installs.
3. The verdict — the guilty commit, the mechanism traced through its diff, and a tested recommendation: clean revert or forward fix.

Handles flaky symptoms (multi-run oracle), merge-heavy history, and tells you up front how many steps the binary search will take.

More like this

Part of a toolbox of skills that do real work — see tokyubevoxelverse/skills.

License

MIT