gitfx-bisectlisted
Install: claude install-skill vivekbhange-hub/git-forensics-skill
# gitfx-bisect: find the commit, then understand it
`git bisect` finds a culprit in about log2(n) steps, but only if every step answers the same
question reliably. Most failed bisects fail on the question, not on git. This skill makes the
question deterministic first, then lets git do the search. It has no script of its own.
## Inputs
- The symptom in one sentence, and how to see it (a command, a test, a URL).
- A commit, tag or date where it worked (good) and one where it fails (bad, usually `HEAD`).
- Permission to check out other commits in the working tree: bisect moves `HEAD`. Ask before
starting, and make sure the tree is clean (`git status --short` prints nothing). Do not run it
in a repository the user does not own or is not authorized to change.
- Commands below say `python3`; on Windows use `python` (or `py -3`).
## Outputs
- `gitfx/bisect-report.md`: symptom, the exact test command, good and bad commits, the culprit
commit hash, subject and date, the files it touched, the reason it broke things, and the fix.
- In chat: the culprit in one sentence, with the evidence, and the state the repo was left in.
## Steps
1. **Write the test first.** A script or test that exits 0 when the bug is absent and 1 to 124
when it is present, runs in under a minute, needs no network or manual step and does not
depend on the current time or random data. Run it on `HEAD` (must fail) and on the good
commit (must pass) before bisecting. If either is wrong, fix the te