Bisect Anything
Find the exact commit (or dependency version, config value, or input) that caused a regression by turning it into an automatic pass/fail check and running git bisect run in a separate worktree, then shrink the bad commit to the hunk that matters and explain it. Handles failing tests, changed output, slowdowns, crashes, visual changes, server behaviour, flaky checks, unbuildable commits and merge-heavy history. Use when the user says "what broke this", "find the commit that", "when did this start", "it used to work", "regression", "git bisect", "which version broke it", or "which change made it
Install
npx skills add dotslashsimran/simcraft --skill bisect-anythinggit clone --depth 1 https://github.com/dotslashsimran/simcraft.git /tmp/simcraft
mkdir -p ~/.claude/skills
cp -r /tmp/simcraft/skills/coding/bisect-anything ~/.claude/skills/bisect-anythingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Bisect anything A bisect is only as good as its oracle: the command that says "good" or "bad" for one commit. Almost every wrong bisect answer comes from an oracle that is flaky, tests the wrong thing, or calls a broken build "bad". So spend most of the effort on the oracle, prove it on both ends, and let the scripts do the rest. Scripts are in `~/simcraft/skills/coding/bisect-anything/scripts/` (Python 3.9+, standard library only). Details, recipes and pitfalls are in `reference.md` next to this file. ## 1. Pin down the regression Ask only for what is missing, one question at a time: - **What is wrong**, as something a command can check (a failing test, a wrong number, a slow page, a crash, a changed screenshot). - **A good point**: a tag, release, date or commit where it worked. If nobody knows, try an old tag; checking one old commit is cheap. - **The bad point**: usually `HEAD`. - **How to build and install** at an old commit. ## 2. Write the oracle Exit `0` good, `125` cannot test this commit, any other code bad. Keep the oracle script **outside the repo** (or pass it with `--overlay`), because old commits do not have it. Pick the recipe that fits; full versions are in `reference.md`: | Regression | Oracle | |---|---| | A test fails | run that one test only, with `--overlay` if the test is new | | Output changed | `oracles/golden_oracle.py`, with `--ignore` for times, versions and ids |
Details
- Skill name
bisect-anything- Repository
- dotslashsimran/simcraft
- Path
skills/coding/bisect-anything/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Bisect Anything skill do?
Find the exact commit (or dependency version, config value, or input) that caused a regression by turning it into an automatic pass/fail check and running git bisect run in a separate worktree, then shrink the bad commit to the hunk that matters and explain it. Handles failing tests, changed output, slowdowns, crashes, visual changes, server behaviour, flaky checks, unbuildable commits and merge-heavy history. Use when the user says "what broke this", "find the commit that", "when did this start", "it used to work", "regression", "git bisect", "which version broke it", or "which change made it
How do I install the Bisect Anything skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dotslashsimran/simcraft --skill bisect-anything. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Bisect Anything popular?
It lives in dotslashsimran/simcraft, which has 517 GitHub stars and 39 forks.
Related skills
API Design Review
517dotslashsimran/simcraft
Review the design of an API surface, meaning an HTTP API (OpenAPI spec or route code), an SDK's public classes and functions, or a CLI. Checks naming and consistency, resource modelling, error design (stable codes, RFC 9457 problem details, request ids), versioning and breaking changes, pagination, filtering, idempotency and retries, rate limits, timeouts, long-running operations, webhooks, auth, partial updates, ID, time and money formats, SDK ergonomics and CLI conventions. Uses scripts to lint OpenAPI files, classify changes between two spec versions as breaking or safe, and dump an SDK's p
Benchmark Honestly
517dotslashsimran/simcraft
Build benchmarks that survive scrutiny and catch the classic lies (dead code elimination, lazy results, constant folding, warm caches, coordinated omission, averages hiding GC pauses, unequal work, noisy machines). Defines the question first, controls and discloses the environment, uses warmups, interleaved repeats, medians, bootstrap confidence intervals and Mann-Whitney tests, and ends with a one-line verdict that includes the CI. Bundles a command runner, an environment reporter and an open-loop latency tester. Use when the user says "benchmark this", "is this faster", "compare performance"
Brand Kit
517dotslashsimran/simcraft
Learn a company's brand design from its live website (colours, fonts with the real font files, logo, button and card shapes, texture, image style) and save it as a reusable kit that vox-explainer and image-gen apply automatically. Use FIRST, before any brand or sponsored video, sticker, graphic or asset for a company (e.g. "a video for Devin", "ChatGPT-style stickers", "match their brand"), or when asked to get, learn, extract or match a brand's look.
Resolving Merge Conflicts
211iamyoki/qwen-image-2.1-skill
Use when you need to resolve an in-progress git merge/rebase conflict.
Git Helper
291joshuadavidthomas/opencode-agent-skills
Provides git workflow assistance, branch management, and commit message optimization
Address Github Comments
514Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.