bisect

Engineering Community

Skill notes

Step 1: Ensure clean working tree

Check that there are no staged or unstaged changes. If there are, stop and tell the user they need a clean working tree before bisecting, since git bisect checks out older commits. If the output is non-empty, stop and ask the user to commit or stash their changes first.

Step 2: Determine the test command

Use $ARGUMENTS to understand what the user wants to test. This should describe a command or check that fails on the current commit. Determine the exact shell command to run.

Step 3: Verify the current commit is bad

Run the test command on the current commit (HEAD). If it passes (exits 0), stop and tell the user — the current commit doesn't exhibit the failure, so there's nothing to bisect.

Step 4: Find a good commit

Start searching backwards from HEAD in steps of 10 commits to find a commit where the test passes. Run the test command. If it still fails, go back another 10 commits (HEAD~10 from the current position). Repeat until either: A passing commit is found, or You've gone back 100+ commits without finding a passing one — stop and ask the user for guidance (maybe a known-good commit SHA). Once a good commit is found, note its SHA.

Step 5: Run git bisect

Return to the original branch first, then start bisecting: Git will check out a middle commit. Run the test command on it: If the test fails → git bisect bad If the test passes → git bisect good Repeat until git reports the first bad commit.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ryanb · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview bisect.preview
# Step 6: Record the result and clean up

git bisect reset

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.