Skip to content

DerpleDude/rgmercs / .claude/skills/debug-new-code

debug-new-code

Verified

Procedure for debugging newly written rgmercs code that misbehaves in game. Use when a recent change produces wrong behavior, errors, or flaky results and the cause isn't obvious. Don't use for one-line typos or syntax errors.

Examine everything thoroughly before patching — fixing one symptom at a time wastes effort.

  1. Instrument first, hypothesize second. Add debug output, read the full logs, then form a hypothesis — don't react to individual symptoms.
  2. Examine the entire flow including async boundaries (actor messages, mq.delay, callbacks). Trace every state transition; don't stop at the first problem.
  3. Fix root causes comprehensively. Address all identified issues together — one solid fix that handles all edge cases beats a chain of patches.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall