Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and confidence levels.
88
82%
Does it follow best practices?
Impact
100%
2.27xAverage score across 3 eval scenarios
Passed
No known issues
Script usage and report generation
Uses bisect script
0%
100%
Uses --good parameter
0%
100%
Test command exit code convention
70%
100%
Focused test command
100%
100%
Report saved to file
100%
100%
Report: First Bad Commit
100%
100%
Report: Confidence Level
100%
100%
Report: Tested Commits
100%
100%
Report: Bisect Log
100%
100%
Correct bad commit identified
100%
100%
Flaky test retry configuration
Uses bisect script
0%
100%
Uses --retries flag
0%
100%
Retries value 3–5
0%
100%
Report: High confidence
0%
100%
Report: Assumptions mentions retries
0%
100%
Report saved to file
100%
100%
Build step and timeout usage
Uses bisect script
0%
100%
Uses --timeout flag
0%
100%
Timeout value is reasonable
50%
100%
Test command includes build step
100%
100%
Uses --bad for non-HEAD revision
100%
100%
Uses --repo flag
0%
100%
Report: Assumptions with timeout
100%
100%
Report saved to file
100%
100%
0f00a4f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.