git-bisect-debugging

Identify the exact commit that introduced a bug in Git repositories.

13|1|Updated Oct 10, 2025

Search Tags:#git #debugging #regression #bisect #bug-tracking #commit-history

Ready to run

npx skills add https://github.com/sjungling/claude-plugins --skill git-bisect-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-bisect-debugging
Source: https://github.com/sjungling/claude-plugins/tree/main/plugins/workflow/skills/git-bisect-debugging
Command: npx skills add https://github.com/sjungling/claude-plugins --skill git-bisect-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically identifies which specific commit introduced a bug or regression in your codebase, eliminating guesswork and saving debugging time.

Core Features & Use Cases

Systematic Binary Search: Efficiently narrow down commit ranges using git bisect algorithms.
Multiple Verification Approaches: Supports automated test scripts, manual verification, or hybrid methods for different scenarios.
Use Case: When your login tests started failing in the last 50 commits, use this Skill to automatically find the exact commit that caused the failure.

Quick Start

I'm using git-bisect-debugging to find which commit introduced this issue.

Frequently Asked Questions about git-bisect-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find which commit introduced a bug in my Git repository?▼

Git bisect uses binary search to identify the exact commit that broke your code. It systematically narrows the commit range by testing midpoints, requiring you to mark each as good or bad until the culprit is found.

Can I automate commit verification when debugging regressions with git bisect?▼

Yes, git bisect supports scripted verification through test automation, manual checks, or hybrid workflows. You can supply a test script to automatically evaluate each commit, or manually verify and mark commits as the bisect progresses.

What's the fastest way to narrow down a bug across 50 recent commits?▼

Binary search via git bisect is the fastest approach, reducing 50 commits to roughly 6 test iterations. Combined with automated verification scripts, you isolate the regression-causing commit without testing every intermediate change.

Do I need special setup or prerequisites to use git bisect for debugging?▼

You need a Git repository with a known good commit (before the bug) and a known bad commit (after the bug). The Skill handles the rest, walking you through strategy selection, verification, and root-cause handoff in a structured four-phase process.

When should I use git bisect instead of manually reviewing recent commits?▼

Use git bisect when the bug spans more than a few commits or you need certainty about the exact culprit. Manual review becomes inefficient beyond ~10 commits; bisect's logarithmic search saves time and eliminates guesswork across larger windows.

What's the difference between automated and manual bisect workflows?▼

Automated workflows run test scripts on each commit, returning pass/fail without human judgment. Manual workflows require you to verify and classify each commit. Hybrid approaches combine both, using automation where reliable and manual checks for edge cases.