Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From loopkit
Uses git bisect to find the exact commit that introduced a bug. Run when something worked before and broke, and you don't know which change did it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loopkit:bisect-regressionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
git bisect start; git bisect bad <bad>; git bisect good <good>.git bisect good/bad.git bisect reset. Report: the commit, the line, the one-sentence cause.
Automate it: git bisect run ./repro.sh if you have a script that exits non-zero on the bug.npx claudepluginhub archive228/loopkitPinpoints the commit introducing a bug or regression using git bisect binary search. For performance regressions, recent test failures, or issues that previously worked.
Use git bisect to binary-search commit history and identify the exact commit that introduced a regression.
Automates git bisect to pinpoint the commit introducing a regression by running tests during binary search, showing diff and blame info, and generating analysis reports.