디버깅
Swamp Troubleshooting Skill
Navigate swamp source code to trace error origins, identify execution flows, inspect internal data structures, and understand CLI behavior when --help is insufficient. Use this skill whenever something is broken ("error", "failing", "not working", "crash", "timeout", "bug", "fix", "debug", "troubleshoot", "root cause", "stack trace", "isn't being found", "giving me an error", "slow", "performance", "latency") OR when you need to understand how swamp works internally ("how does", "what happens when", "where is", "internals", "under the hood"). Applies even when the query mentions a specific domain (e.g., "vault expressions aren't resolving" or "how does extension push work") — fetch swamp source to find the answer.