Binary Search Debugging
Using bisect/git bisect to isolate failure to exact commit or code path.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill binary-search-debugginggit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/binary-search-debugging ~/.claude/skills/binary-search-debuggingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Binary Search Debugging Efficiently narrowing problem scope through bisection. ## Context You are using binary search to isolate a failure. Works for bugs and regressions. ## Domain Context - **Git Bisect**: Half the commits; does bug exist here? Repeat until you find the culprit commit - **Code Path**: Disable half the code; does bug reproduce? Narrow to affected code - **Data Range**: Bugs with specific input; binary search the input space - **Time Range**: Regression over time; binary search commits ## Instructions 1. **Identify Good and Bad Commits**: When did it work? When did it break? 2. **Run Git Bisect**: Automates binary search through commits 3. **Test at Bisect Point**: Does bug exist at this commit? 4. **Bisect Reports**: It, narrows range automatically 5. **Find Exact Commit**: Run to completion; identifies culprit 6. **Review Commit**: What changed? Why does it cause the bug? 7. **Code Path Bisect**: Disable features/code paths; find what triggers bug ## Anti-Patterns - Assuming recent commit caused it; test assumptions with bisect - Not using bisect on large commit ranges; manual search is slow - Bisecting without reproducible test; need consistent yes/no answer - Not reviewing found commit; understanding the bug matters ## Further Reading - Git bisect documentation - Linux kernel debugging; git bisect is standard there
Details
- Skill name
binary-search-debugging- Repository
- sethdford/claude-skills
- Path
engineer/debugging/skills/binary-search-debugging/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Binary Search Debugging skill do?
Using bisect/git bisect to isolate failure to exact commit or code path.
How do I install the Binary Search Debugging skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Binary Search Debugging popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Bug Bounty Program
48sethdford/claude-skills
Establish and manage bug bounty programs to leverage external researchers for vulnerability discovery.
Beta Program Design
48sethdford/claude-skills
Launch and go-to-market skill for product managers.
Build Vs Buy
48sethdford/claude-skills
Systematically evaluate whether to build a solution or buy/use existing product. Use when evaluating tooling, services, or frameworks.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.