git-bisect

Automate Git bisect sessions to identify regression-introducing commits.

1|Updated Jan 26, 2026

Search Tags:#automation #git #debugging #version control #regression testing #bug hunting

Ready to run

npx skills add https://github.com/manastalukdar/claude-devstudio --skill git-bisect-manastalukdar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of finding the exact commit that introduced a bug in your codebase using Git's binary search capabilities, significantly reducing debugging time.

Core Features & Use Cases

Automated Bug Hunting: Pinpoints the commit responsible for a regression.
Test Script Integration: Executes provided or generated test scripts to validate commits.
Session Management: Saves and resumes bisect sessions, handling untestable commits and flaky tests.
Use Case: You've noticed a bug in your application, but you're unsure when it was introduced. This Skill will systematically go through your commit history, running your test suite at each step, to identify the precise commit that caused the issue.

Quick Start

Use the git-bisect skill to automatically find the commit that introduced a bug, starting from the current HEAD and using 'npm test' as the validation command.

Frequently Asked Questions about git-bisect

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

FAQPage Schema

How do I find the exact commit that introduced a regression in my Git repository?▼

Automating Git bisect finds the exact commit that introduced a regression by using binary search across your commit history and executing test scripts to pinpoint the culprit commit.

Can I use an automated test command like 'npm test' to validate commits during a bug hunt?▼

Yes, you can use an automated test command like 'npm test' to validate commits during a bug hunt. The skill executes provided or generated test scripts at each step to determine if a commit is good or bad.

What is the best way to handle untestable commits or flaky tests when debugging version history?▼

Handling untestable commits or flaky tests during version history debugging is managed through built-in session management, which skips problematic commits and resumes bisect sessions to maintain accuracy.

Do I need a specific test execution environment to run automated Git bisect?▼

Yes, you need Git and a test execution environment to run automated Git bisect. These dependencies are required to validate commits and identify regressions through the binary search process.

How does binary search debugging work for finding bugs in a codebase?▼

Binary search debugging for finding bugs works by systematically navigating commit history, running your test suite at each step to narrow down the search range until it identifies the precise commit that caused the issue.