bisect

Automates git bisect with automated build and test to identify the first bad commit.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/kindofluke/albatross-data --skill bisect-kindofluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bisect
Source: https://github.com/kindofluke/albatross-data/tree/main/.vibe/skills/bisect
Command: npx skills add https://github.com/kindofluke/albatross-data --skill bisect-kindofluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find which commit introduced a bug by comparing behavior across a range of commits. Uses git bisect with automated build and test. Use when a bug appeared recently and you need to identify the culprit commit.

Core Features & Use Cases

  • Automated Bisect workflow: Start a bisect with a good and bad commit, let the system build and test across the range.
  • Mode 2: Manual Comparison: Compare outputs and logs between two specific commits to pinpoint code-path differences and performance shifts.
  • Optional pipeline reporting: Analyze last good vs first bad logs to quantify regression details.

Quick Start

Run a bisect on your repository by providing a good commit, a bad commit, and a test command to automatically identify the first bad commit.

Frequently Asked Questions about bisect

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

FAQPage Schema
How do I find which commit introduced a bug using git bisect?

Automated git bisect identifies the exact buggy commit by running your specified test command across a commit range between a known good and bad commit. The system automatically builds, tests, and narrows down the regression to pinpoint the culprit.

Can I compare outputs between two specific commits to diagnose a regression?

Manual comparison mode compares outputs and logs between two specific commits to diagnose regressions. This workflow pinpoints code-path differences and quantifies performance shifts without running a full automated bisect.

What do I need to start an automated bisect on my repository?

Starting an automated bisect requires a known good commit, a known bad commit, and a test command. The system uses these inputs to automatically build and test across the commit range to find the regression.

Does git bisect report the differences between the last good and first bad commit?

Optional pipeline reporting analyzes the last good versus first bad logs to quantify regression details. This feature reports diffs and context to help you understand what specifically changed in the buggy commit.

When should I use automated bisect instead of manual commit comparison?

Use automated bisect when a bug appeared recently and you need to identify the culprit commit across a wide range. Use manual comparison when you suspect two specific commits and want to compare their logs and code-path differences directly.