Maps GitHub Actions CI runs to git commits and identifies suspect ranges between last known good and first known bad commits.
Identifies suspect commits by mapping GitHub Actions CI runs to git history between last known good and first known bad.
/plugin marketplace add bengous/claude-code-plugins/plugin install git-tools@bengous-pluginsbisect-ci/Maps GitHub Actions CI runs to git commits and identifies suspect ranges between last known good and first known bad commits.
/bisect-ci
/bisect-ci --branch feature/my-branch
/bisect-ci --branch main --output debug/results.txt
/bisect-ci --limit 50
--branch <name> - Branch to analyze (default: current branch)--output <file> - Output file path (default: temp/ci-bisect-TIMESTAMP.txt)--limit <num> - Number of CI runs to fetch (default: 100)╔═══════════════════════════════════════════════════════════════
║ SUSPECT RANGE START (HEAD) - Bug still present
╚═══════════════════════════════════════════════════════════════
abc1234 commit message ◄── FAILURE https://github.com/.../runs/123 [HEAD/SUSPECT]
...
[All commits in suspect range marked with [SUSPECT]]
...
╔═══════════════════════════════════════════════════════════════
║ SUSPECT RANGE END - Bug introduced somewhere between here and HEAD
╚═══════════════════════════════════════════════════════════════
xyz9876 commit message ◄── SUCCESS https://github.com/.../runs/456 [LAST KNOWN GOOD]
Execute the bisect-ci script with arguments: $ARGUMENTS