skills.rest
MGriot
MGriotCOMMUNITY
Explore all skills by this author →
GitHub

git-bisector

Pinpoint the first bug-introducing commit via binary search over git history.

Updated Jan 31, 2026
Search Tags:#git#debugging#version-control#bug#binary-search#git-bisect
One-click install
npx skills add https://github.com/MGriot/.gemini --skill git-bisector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-bisector
Source: https://github.com/MGriot/.gemini/tree/main/skills/git-bisector
Command: npx skills add https://github.com/MGriot/.gemini --skill git-bisector

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Git Bisector identifies the first commit that introduced a bug by performing a guided binary search over git history, significantly reducing the time to locate regressions.

Core Features & Use Cases

  • Binary search across commits to isolate the first bad commit.
  • Supports both manual and automated bisect workflows with clear preparation and cleanup steps.
  • Useful for debugging regressions in any git-managed project by providing reproducible steps and commands.

Quick Start

To begin a bisect session:

  • git bisect start
  • git bisect bad
  • git bisect good <commit> To automate the process:
  • git bisect run <script> When finished, reset to the original state:
  • git bisect reset

Frequently Asked Questions about git-bisector

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

FAQPage Schema
How do I find the exact commit that introduced a bug in git?▼

You can find the exact commit that introduced a bug using git bisect to perform a binary search over your repository history, significantly reducing the time needed to locate regressions.

Can I automate a git bisect workflow to run tests across commits?▼

Yes, you can automate the git bisect workflow by running a script with the git bisect run command, enabling the system to automatically test commits and narrow down the regression.

What are the steps to start a git bisect session for debugging a regression?▼

To start debugging a regression, initialize the session with git bisect start, mark the current state as bad with git bisect bad, and provide a known good past commit using git bisect good.

Do I need a known good past state to use git binary search for bug isolation?▼

Yes, git binary search for bug isolation requires a known good past state and a current broken state to effectively narrow down and determine the exact commit that introduced the regression.

How do I reset my repository after finishing a git bisect session?▼

After finishing a git bisect session, you reset your repository to its original state by running the git bisect reset command, ensuring proper cleanup of the bisect workflow.

What is the best way to debug regressions in any git-managed software project?▼

The best way to debug regressions in a git-managed project is using a guided binary search workflow, which provides reproducible steps and commands to isolate the first bad commit deterministically.

Related Skills

Explore More Software Engineering Skills→
KentoShimizuKentoShimizu
7

git-bisect-debugging

Identify first bad commits using deterministic git bisect workflows.

Community
Advanced
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Official
Advanced
ArabelaTsoArabelaTso
142

bisect-aware-instrumentation

Instrument code to produce deterministic pass/fail signals for git bisect runs.

Community
Advanced
penpotpenpot
58.3k

backport-commit

Manually apply a Git commit diff to the current branch.

Official
Advanced