bisect

Automate Git bisect to identify regression-introducing commits with build and test execution.

1.0k|109|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/sirius-db/sirius --skill bisect-sirius-db
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bisect
Source: https://github.com/sirius-db/sirius/tree/main/.claude/skills/bisect
Command: npx skills add https://github.com/sirius-db/sirius --skill bisect-sirius-db

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers pinpoint the exact commit that introduced a bug in their codebase, saving significant debugging time.

Core Features & Use Cases

  • Automated Git Bisect: Leverages git bisect to efficiently search through commit history.
  • Automated Build & Test: Integrates with build processes and test commands to verify each commit.
  • Use Case: When a new feature suddenly breaks the build or a test fails, use this Skill to automatically identify which code change caused the issue.

Quick Start

Use the bisect skill to find the commit that introduced a bug, starting from 10 commits ago to the current commit, by running the command 'make test'.

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 regression using Git bisect?

Git bisect identifies the commit that introduced a regression by automating the binary search through commit history, running build and test commands at each step to validate code changes efficiently.

Can I use custom test commands to automate Git bisect for build failures?

Yes, automated Git bisect supports custom test commands like 'make test' to verify each commit, gracefully skipping commits that fail to build while narrowing down the exact regression point.

How does Git bisect handle SQL query validation during regression testing?

Git bisect supports SQL query validation against a DuckDB CPU baseline, executing queries at each commit step to detect regressions in database logic and pinpoint the exact code change that caused the issue.

What is the best way to automatically locate a bug across a range of commits?

Automated Git bisect is the best way to locate a bug across a specified range of commits, integrating automated build execution and test validation to efficiently identify the exact code change that introduced the regression.

Why does Git bisect skip commits that fail to build during regression testing?

Git bisect skips commits that fail to build to handle build failures gracefully, ensuring the automated regression testing process continues smoothly without getting stuck on broken intermediate commits.

Do I need a specific testing framework to identify a regression with Git bisect?

No specific testing framework is required; Git bisect integrates with your existing build processes and custom test commands, allowing you to use any command like 'make test' to validate commits and find regressions.