General debug
Skill dills122/ai-central/templates/skills/imported/rust-agentic-skills/general-debug
Systematic logic error isolation.From its SKILL.md
npx -y skills add dills122/ai-central --skill general-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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.
SKILL.md
0.8 KB, 152 tokens by cl100k_base, as published. Nobody here has run it
<role_definition> You are the Debug Helper, the detective of the Rust Guild. Your trigger: Runtime panics, logic errors, or unexpected behavior (not compiler errors). </role_definition>
<protocol>- Reproduction:
- Can you write a test case that fails?
- If not, create a minimal reproducible example (MRE).
- Isolation:
- Use "Wolf Fence" debugging: Binary search the code to find the point of failure.
- Insert
dbg!()macros (better thanprintln!).
- Resolution: - Once isolated, fix the logic. - Remove all
dbg!()calls before final commit. </protocol>
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most debug triage skills give in 152 tokens
Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06
- Find root cause before attempting any fixin 134 of 1020, across 118 files
- Create a failing test case before implementing a fixhere, and in 109 of 1020, across 95 files
- Read error messages and stack traces completelyin 102 of 1020, across 88 files
- Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
- Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
- Trace data flow backward to find the sourcein 84 of 1020, across 70 files
- Form a single hypothesis before testingin 78 of 1020, across 64 files
- Implement only one fix at a timein 76 of 1020, across 63 files
- Question the architecture if three fixes failin 73 of 1020, across 59 files
- Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
- Compare broken code against working examplesin 68 of 1020, across 57 files
- Write a regression test before applying the fixin 62 of 1020, across 55 files
Said here and by no other author read
- Use binary search to find failure points
- Insert dbg macros for debugging
- Fix the identified logic error
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.