Debug by bisection
Skill duliangkuan/cc-clone/examples/demo-brain/skills/debug-by-bisection
Clone a Claude Code brain — package/redact/distribute memory, skills, agents & rules; one-click install others' brains; export to Codex/Gemini/Cursor/OpenCode.
npx -y skills add duliangkuan/cc-clone --skill debug-by-bisectionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Find the cause of a regression by systematically halving the search space (git bisect, feature flags, input reduction).
SKILL.md
0.5 KB, as published. Nobody here has run it
Debug by Bisection
- Establish a reliable repro (a command that fails deterministically).
- Find a known-good point in the past.
- Bisect: git bisect between good and bad, or binary-search the input/config.
- At each step, keep the repro identical. Change one variable only.
- Stop when one commit/flag/input flips pass→fail. That's the cause.