skills.rest
jmagly
jmaglyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

regression-bisect

Automate git bisect to find the commit that introduced a regression.

175|26|Updated Aug 14, 2025
Search Tags:#debugging#root cause analysis#regression testing#automated testing#commit analysis#git bisect
One-click install
npx skills add https://github.com/jmagly/aiwg --skill regression-bisect-jmagly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-bisect
Source: https://github.com/jmagly/aiwg/tree/main/plugins/sdlc/skills/regression-bisect
Command: npx skills add https://github.com/jmagly/aiwg --skill regression-bisect-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of identifying the exact commit that introduced a regression or bug in your codebase, saving significant debugging time.

Core Features & Use Cases

  • Automated Git Bisect: Uses git bisect to efficiently binary search through commit history.
  • Test Integration: Runs automated tests at each commit to pinpoint the failure.
  • Root Cause Analysis: Provides detailed information about the breaking commit, including diffs and blame.
  • Use Case: When a feature suddenly stops working, you can trigger this skill with a known good and bad commit, and it will automatically find the culprit commit.

Quick Start

Use the regression-bisect skill to find the commit that broke the authentication feature.

Frequently Asked Questions about regression-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 bug in my codebase?▼

To find the exact commit that introduced a bug, you can automate a binary search through your commit history using git bisect. This process executes automated tests at each step to quickly pinpoint the failing commit.

What is the best way to automate root cause analysis for a regression?▼

Automating root cause analysis for a regression involves executing a binary search across commit history with git bisect. It runs your automated tests iteratively to identify the precise breaking commit and provides blame information.

Can I use git bisect with my existing CI/CD pipelines and testing frameworks?▼

Yes, you can use git bisect with your CI/CD pipelines and testing frameworks. The regression analysis process integrates with your existing automated tests to validate each commit during the binary search.

How do I trigger a binary search if I only have a known good and bad commit?▼

To trigger a binary search with a known good and bad commit, provide both references to start the git bisect process. The automated search will then iterate through intermediate commits, running tests until the culprit is found.

What information do I get when git bisect identifies the breaking commit?▼

When git bisect identifies the breaking commit, it provides detailed root cause analysis including the specific commit blame information, diff context, and potential fix suggestions to help resolve the regression.

Related Skills

Explore More Software Engineering Skills→
KentoShimizuKentoShimizu
7

git-bisect-debugging

Identify first bad commits using deterministic git bisect workflows.

Community
Advanced
robit-manrobit-man

regression-bisect

Automate git bisect to identify the commit that introduced a regression.

Community
Advanced
huuhiep0303huuhiep0303

ci-cd-and-automation

Automate CI/CD pipeline setup with GitHub Actions quality gates and testing.

Community
Advanced
Lionad-MorotarLionad-Morotar
7

debug-by-commits

Binary search Git commit history to identify regression-introducing commits.

Community
Intermediate