DerpleDude/rgmercs / .claude/skills/debug-new-code
debug-new-code
VerifiedProcedure 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.
- Instrument first, hypothesize second. Add debug output, read the full logs, then form a hypothesis — don't react to individual symptoms.
- Examine the entire flow including async boundaries (actor messages,
mq.delay, callbacks). Trace every state transition; don't stop at the first problem. - Fix root causes comprehensively. Address all identified issues together — one solid fix that handles all edge cases beats a chain of patches.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |