Systematic debugging with defense-in-depth approach (symptoms → immediate cause → root cause → systemic issues → prevention). Auto-activates when user mentions "error", "failing", "broken", "debug", "bug", "issue" or when /ccpm:verify runs. Uses Observe → Hypothesize → Test → Confirm → Fix → Verify → Document workflow. Updates Linear with findings and automatically logs blockers that require external fixes. Traces root causes instead of patching symptoms. Integrates with ccpm-code-review to verify fixes pass all gates before marking complete. Suggests binary search for intermittent issues and five-whys analysis for complex problems.
View on GitHubJanuary 24, 2026
Select agents to install to:
npx add-skill https://github.com/duongdev/ccpm/blob/main/skills/ccpm-debugging/SKILL.md -a claude-code --skill ccpm-debuggingInstallation paths:
.claude/skills/ccpm-debugging/# CCPM Debugging Systematic debugging with Linear integration and structured troubleshooting workflow. ## When to Use This skill auto-activates when: - User mentions: **"error"**, **"failing"**, **"broken"**, **"debug"**, **"bug"**, **"issue"** - Running **`/ccpm:verify`** command - Tests failing during `/ccpm:verify` - Build errors during implementation - Runtime errors or exceptions - Unexpected behavior ## Core Debugging Philosophy ### Defense-in-Depth Approach **Multiple layers of investigation**: 1. **Symptoms** - What's observable? 2. **Immediate cause** - What directly caused the error? 3. **Root cause** - Why did it happen? 4. **Systemic issues** - Could this happen elsewhere? 5. **Prevention** - How to prevent recurrence? ### Systematic Process ``` Observe → Hypothesize → Test → Confirm → Fix → Verify → Document ``` Never skip steps. Each step builds on the previous. ## Integration with CCPM ### Use with `/ccpm:verify` When verification fails, this skill provides structured debugging: ``` User: "/ccpm:verify AUTH-123" Claude: [ccpm-debugging activates] Starting systematic debugging for AUTH-123... Step 1: GATHER SYMPTOMS Running /ccpm:verify to collect error information... Found failures: - 3 failing tests - 1 TypeScript compilation error - 0 linting errors Step 2: ANALYZE FAILURES Test failures: 1. test/auth/login.test.ts:45 ❌ "should handle invalid credentials" Expected: 401 Unauthorized Actual: 500 Internal Server Error 2. test/auth/jwt.test.ts:78 ❌ "should refresh expired tokens" Error: Cannot read property 'id' of undefined 3. test/api/protected.test.ts:23 ❌ "should reject missing tokens" Timeout: Request exceeded 5000ms TypeScript error: src/auth/jwt.ts:45:12 - error TS2345: Argument of type 'string | undefined' is not assignable to parameter of type 'string' Step 3: FORM HYPOTHESES Hypothesis 1: JWT token handling has type safety issue (TS error) Hypothesis 2: Error handling missing (test 1 shows 500 inst