skills.rest
duongdev
duongdevCOMMUNITY
Explore all skills by this author →
Website𝕏@duongdevGitHub

ccpm-debugging

Diagnose software failures using defense-in-depth debugging and five-whys.

9|1|Updated Nov 20, 2025
Search Tags:#code quality#debugging#troubleshooting#bug fix#root cause analysis#verification#linear
One-click install
npx skills add https://github.com/duongdev/ccpm --skill ccpm-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ccpm-debugging
Source: https://github.com/duongdev/ccpm/tree/main/skills/ccpm-debugging
Command: npx skills add https://github.com/duongdev/ccpm --skill ccpm-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the frustration of chaotic debugging by providing a systematic, defense-in-depth approach to identify, trace, and resolve software issues. It ensures every bug fix is thorough, verified, and documented, preventing recurrence and saving development time.

Core Features & Use Cases

  • Systematic Troubleshooting: Guides you through observing symptoms, forming hypotheses, testing, confirming, fixing, verifying, and documenting.
  • Root-Cause Tracing: Employs techniques like the "5 Whys" to uncover the true origin of problems, not just symptoms.
  • Linear Integration: Automatically updates Linear tasks with debugging progress, findings, and blockers, keeping your project management in sync.
  • Use Case: When your CI/CD pipeline fails intermittently with a "database connection timeout," this skill will guide you through diagnosing network, configuration, or readiness issues, helping you implement a robust health check and document the fix in Linear.

Quick Start

When tests are failing, use the /ccpm:verification:fix AUTH-123 command. The debugging skill will activate automatically to guide you through the fix.

Frequently Asked Questions about ccpm-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically debug failing tests and CI/CD pipeline failures?▼

Systematic debugging involves observing symptoms, forming hypotheses, testing them, confirming root causes, implementing fixes, and verifying results. This skill guides you through that structured workflow, using techniques like binary search and five-whys to trace problems to their origin rather than treating surface symptoms.

What's the best way to find the root cause of intermittent or hard-to-reproduce bugs?▼

Root cause analysis uses defense-in-depth troubleshooting and the five-whys technique to move beyond symptoms to underlying issues. This skill automates that process, testing hypotheses methodically and documenting findings in Linear so fixes address the true problem, not just its effects.

Can I track debugging progress and blockers in Linear while fixing code issues?▼

Yes. This skill integrates directly with Linear, automatically logging debugging progress, findings, and blockers as you work through failures. Your project management stays in sync with your troubleshooting without manual updates.

How do I verify a bug fix is complete and prevent the same issue from recurring?▼

Verification captures the entire fix workflow: testing your solution against the original failure, documenting what you learned, and updating project records. This comprehensive approach prevents recurrence by ensuring fixes are thorough and knowledge is captured.

Does this debugging approach work with compilation failures, runtime exceptions, and test failures?▼

Yes. This skill handles error, failing, and broken code scenarios across compilation failures, runtime exceptions, test failures, and intermittent issues using the same systematic troubleshooting method adapted to each failure type.

What's the difference between fixing a bug quickly and debugging systematically?▼

Quick fixes often address visible symptoms; systematic debugging traces root causes. This skill ensures every fix is thorough, verified, and documented, saving time overall by preventing recurring issues and reducing time spent on incomplete solutions.

Related Skills

Explore More Software Engineering Skills→
buiducnhatbuiducnhat
52

fix

Diagnose software bugs through root-cause analysis and implement verified fixes.

Community
Intermediate
oliver-kriskaoliver-kriska
517

phx:learn

Records bug-fix patterns and lessons learned into a central file.

Community
Basic
TymorIbrahimTymorIbrahim

verification-loop

Automate build, type, lint, test, security, and diff checks for Claude Code sessions.

Community
Advanced
trungdo9trungdo9
3

debugging

Guide systematic software debugging with root cause tracing and validation.

Community
Advanced