Instrument code to support efficient git bisect by producing deterministic pass/fail signals and concise runtime summaries for each tested commit. Use when debugging regressions with git bisect, automating bisect workflows, creating bisect test scripts, handling flaky tests during bisection, or needing clear exit codes and logging for automated bisect runs. Helps identify the exact commit that introduced a bug through automated testing.
92
92%
Does it follow best practices?
Impact
86%
1.30xAverage score across 3 eval scenarios
Passed
No known issues
Bisect exit code correctness
Build failure skip
100%
100%
Good exit code
100%
100%
Bad exit code
100%
100%
Timeout as skip
50%
100%
No fatal exit codes
100%
100%
WIP commit skip
0%
100%
Per-commit log file
0%
100%
Commit hash in log
62%
100%
Result in log
100%
100%
Script executable
100%
100%
Flaky test determinism handling
Multiple test runs
100%
100%
All pass → good
100%
100%
All fail → bad
100%
100%
Mixed results → skip
100%
100%
RANDOM_SEED set
0%
100%
TZ=UTC set
0%
100%
Temp cache cleanup
40%
100%
Pass count tracked
50%
100%
Skip message logged
100%
100%
Performance regression bisection
Performance threshold comparison
100%
100%
Skip on measurement failure
100%
100%
Python wrapper used
100%
100%
Wrapper --performance-threshold flag
0%
0%
Wrapper --retries flag
0%
0%
Wrapper --timeout flag
0%
0%
JSON log per commit
50%
40%
State directory
0%
0%
Skip range used
100%
100%
Build failure skipped
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.