bisect - Bisect a bug to identify its introducing commit
Reproduces an issue across Git history to determine whether the bug is a regression and identify the introducing commit and pull request.
Tags
Updated: 2026-10-05Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Parse issue reproduction steps
- Prepare an isolated worktree
- Reproduce bugs across commits
- Run manual git bisect
- Confirm good and bad commits
- Report the regression verdict
Inputs
- GitHub issue number or URL
- Exact reproduction steps
- Expected and current behavior
- Target platform and OS version
- Git repository checkout
- Browser or device environment
Outputs
- Regression verdict
- Introducing commit
- Introducing pull request
- Bisect results
- Cleaned-up worktree and processes
Requirements
- Git repository access
- GitHub CLI access
- Issue and repository permissions
- Platform-specific test harness
- Browser, simulator, or device tooling
- Consistently reproducible bug at main