Help us improve
Share bugs, ideas, or general feedback.
From cc-general-skills
Apply systematic debugging methodology using medical differential diagnosis principles. Trigger when AI modifies working code and anomalies occur, or when users report unexpected test results or execution failures. Use observation without preconception, fact isolation, differential diagnosis lists, deductive exclusion, experimental verification, precise fixes, and prevention mechanisms.
npx claudepluginhub iciakky/cc-general-skills --plugin cc-general-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/cc-general-skills:skills/debugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill applies a systematic debugging methodology inspired by medical differential diagnosis. It provides a rigorous 7-step process for investigating and resolving bugs through observation, classification, hypothesis testing, and verification. This approach prioritizes evidence-based reasoning over assumptions, ensuring root causes are identified rather than symptoms treated.
Enforces systematic root cause analysis before fixes for bugs, test failures, unexpected behavior, performance issues, and build failures.
Enforces systematic root cause investigation for bugs, test failures, and unexpected behavior through four phases: investigation, pattern analysis, hypothesis testing, and implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Share bugs, ideas, or general feedback.
This skill applies a systematic debugging methodology inspired by medical differential diagnosis. It provides a rigorous 7-step process for investigating and resolving bugs through observation, classification, hypothesis testing, and verification. This approach prioritizes evidence-based reasoning over assumptions, ensuring root causes are identified rather than symptoms treated.
Activate this skill in two primary scenarios:
Scenario A: Post-Modification Anomalies When modifying a previously tested and working version, and any unexpected behavior emerges after the changes.
Scenario B: User-Reported Issues When users report that test results don't meet expectations or the system fails to execute as intended.
Follow this 7-step systematic approach to diagnose and resolve issues.
For a detailed checklist of each step, refer to {baseDir}/references/debugging_checklist.md. For common bug patterns and their signatures, see {baseDir}/references/common_patterns.md.
Objective: Collect all available evidence without jumping to conclusions.
Process:
Key Principle: Observe, don't just see. At this stage, the goal is comprehensive data collection, not interpretation.
Objective: Distinguish symptoms from root causes and narrow the problem scope.
Process:
For Incremental Development (Scenario A - Post-Modification Anomalies):
General Isolation:
Key Principle: Reduce the search space by eliminating what works correctly.
Objective: Enumerate all possible technical failure points.
Process:
{baseDir}/references/common_patterns.md for known bug patternsKey Principle: Cast a wide net initially—don't prematurely exclude possibilities.
Objective: Systematically eliminate impossible factors to find the truth.
Process:
Key Principle: Evidence-based elimination leads to certainty.
Objective: Validate hypotheses through controlled experiments.
Process:
Key Principle: Prove hypotheses with experiments, not assumptions.
Objective: Apply the most elegant and least invasive solution.
Process:
Key Principle: Seek elegant solutions, not temporary workarounds.
Objective: Ensure the same error doesn't recur and verify stability.
Process:
Key Principle: Fix once, prevent forever.
Maintain Scientific Rigor:
Documentation:
{baseDir}/references/investigation_template.md to structure investigation logs{baseDir}/assets/debug_report_template.md for creating post-mortem reportsCommunication:
This skill includes bundled resources to support the debugging workflow:
Load these into context as needed during investigation:
{baseDir}/references/debugging_checklist.md - Comprehensive checklist for each debugging step{baseDir}/references/common_patterns.md - Common bug patterns and their signatures{baseDir}/references/investigation_template.md - Template for documenting investigationsUse these templates for documentation and reporting:
{baseDir}/assets/debug_report_template.md - Template for summarizing debugging sessions and creating post-mortem reports