bisect
- Repo stars 2,380
- License MIT
- Author updated Live
- Author repo dotfiles
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: bisect
description: Git bisect to find the first bad commit by running a test command. Use git bisect to binary-sear…
category: engineering
runtime: no special runtime
---
# bisect output preview
## PART A: Task fit
- Use case: Git bisect to find the first bad commit by running a test command. Use git bisect to binary-search through commit history and find the first commit that introduced a failure. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Step 1: Ensure clean working tree / Step 2: Determine the test command / Step 3: Verify the current commit is bad” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Git bisect to find the first bad commit by running a test command. Use git bisect to binary-search through commit history and find the first commit that introduced a failure. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Step 1: Ensure clean working tree / Step 2: Determine the test command / Step 3: Verify the current commit is bad” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Start with a small task and check whether the result follows “Step 1: Ensure clean working tree / Step 2: Determine the test command / Step 3: Verify the current commit is bad”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: bisect
description: Git bisect to find the first bad commit by running a test command. Use git bisect to binary-sear…
category: engineering
source: ryanb/dotfiles
---
# bisect
## When to use
- Git bisect to find the first bad commit by running a test command. Use git bisect to binary-search through commit hist…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Step 1: Ensure clean working tree / Step 2: Determine the test command / Step 3: Verify the current commit is bad” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "bisect" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Step 1: Ensure clean working tree / Step 2: Determine the test command / Step 3: Verify the current commit is bad
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}bisect — Find the First Bad Commit
Use git bisect to binary-search through commit history and find the first commit that introduced a failure.
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.
git status --porcelainIf 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.
git stash --include-untracked -q 2>/dev/null; true
git checkout HEAD~10 --quietRun 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 checkout - --quiet
git bisect start
git bisect bad
git bisect good <good-commit-sha>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.
Step 6: Record the result and clean up
Save the first bad commit SHA and message. Then reset:
git bisect resetStep 7: Report
Tell the user the first bad commit, including:
- The commit SHA
- The commit message
- The commit author and date
- A brief
git show --statof the commit so they can see which files changed
Decide Fit First
Design Intent
How To Use It
Boundaries And Review