skills.rest
skylarsabo
skylarsaboCOMMUNITY
Explore all skills by this author →
GitHub

regression-hunt

Bisect version control history to isolate regression-introducing commits and generate reports.

Updated Jun 22, 2026
Search Tags:#version control#codebase analysis#regression detection#bug hunting#commit bisecting
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill regression-hunt-skylarsabo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-hunt
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/rigor/skills/regression-hunt
Command: npx skills add https://github.com/skylarsabo/code-ops --skill regression-hunt-skylarsabo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill is designed to help users quickly pinpoint the commit that caused a regression in their codebase and find related regressions in recent changes.

Core Features & Use Cases

  • Commit Bisecting: Walks through the VCS history to find the exact commit that introduced a regression.
  • Regression Detection: Runs tests across recent changes to identify additional regressions.
  • Report Generation: Creates a detailed report and findings register upon completion.

Quick Start

Invoke the rigor:regression-hunt command to start the regression hunting process.

Frequently Asked Questions about regression-hunt

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 codebase?▼

To find the exact commit that introduced a regression, this Skill executes bisecting on your version control history. It walks through VCS commits to pinpoint the problematic change and generates a detailed report for analysis.

What is the best way to isolate bug-introducing commits in version control?▼

Isolating bug-introducing commits is best done by executing bisecting on your version control history. This process pinpoints the exact problematic commit and identifies related regressions in recent changes.

Can I detect multiple regressions from recent codebase changes at once?▼

Yes, you can detect multiple regressions from recent changes. The regression detection feature runs tests across recent codebase changes to identify additional related regressions alongside the primary problematic commit.

How do I start the commit bisecting process for codebase analysis?▼

To start the commit bisecting process for codebase analysis, invoke the `rigor:regression-hunt` command. This initiates the regression hunting process to walk through your version control history automatically.

Does regression hunting work without any external dependencies?▼

Yes, regression hunting works without external dependencies. The Skill operates independently using internal scripts to perform codebase analysis, execute version control bisecting, and generate detailed findings registers.

Related Skills

Explore More Software Engineering Skills→
klhklh
1

systematic-debugging

Diagnose bugs through a four-phase root cause analysis methodology.

Community
Intermediate
jpoleyjpoley
50

patch-engineer

Validate security patch quality and regression risk for code changes.

Community
Advanced
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
gitgoodordietryinggitgoodordietrying
1

git-workflows

Automate advanced Git workflows with interactive rebase, bisect, and worktree commands.

Community
Advanced