OpenSkillIndex← back to search
claude-code

ToolMaster bug-fix

Systematic bug diagnosis and fix. Use when debugging errors, unexpected behavior, or failing tests. Follows root-cause-first approach.

install
source · Clone the upstream repo
git clone https://github.com/techieharry/ToolMaster
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/techieharry/ToolMaster "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bug-fix" ~/.claude/skills/techieharry-toolmaster-bug-fix && rm -rf "$T"
manifest: skills/bug-fix/SKILL.md
source content

Bug Fix

Process

  1. Reproduce — confirm the bug exists, get exact error/behavior
  2. Isolate — narrow to the smallest code path that triggers it
  3. Root cause — find the actual cause, not just the symptom
  4. Fix — change the minimum code needed
  5. Verify — confirm the fix works AND doesn't break anything else

Rules

  • Never fix symptoms. If a null check "fixes" a crash, find why it's null.
  • Read the error message. The answer is usually in the stack trace.
  • Check git blame — when was this code last changed and by whom?
  • One fix per bug. Don't refactor while fixing.
  • Add a test that would have caught this bug.

Output

  • Root cause: one sentence explaining why the bug exists
  • Fix: the minimal code change
  • Test: how to verify the fix
  • Prevention: what would catch this class of bug in the future