cc-debugging

Diagnose software defects using a scientific debugging workflow.

351|31|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/ryanthedev/code-foundations --skill cc-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-debugging
Source: https://github.com/ryanthedev/code-foundations/tree/main/skills/cc-debugging
Command: npx skills add https://github.com/ryanthedev/code-foundations --skill cc-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, repeatable approach to debugging by applying the scientific method to stabilize, hypothesize, experiment, fix, test, and search for similar defects, reducing guesswork and speeding repair.

Core Features & Use Cases

  • CHECKER mode audits debugging methodology and outputs a status table with violations and warnings.
  • APPLIER mode guides when stuck, offering stabilization strategy, hypothesis formation, and fix-verification guidance.
  • Use cases include diagnosing intermittent failures, crashes, and regressions across development, QA, and production environments.

Quick Start

Start a debugging session by stabilizing the error, formulating a hypothesis, designing an experiment, executing it, and verifying the fix.

Frequently Asked Questions about cc-debugging

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

FAQPage Schema
What is the best way to debug intermittent software failures and crashes?

The best way to debug intermittent failures is applying a scientific debugging workflow: stabilize the error, hypothesize, experiment, fix, test, and search. This disciplined approach reduces guesswork and speeds repair.

How do I find the root cause of a regression using a scientific method?

To find the root cause of a regression, follow the STABILIZE, HYPOTHESIZE, EXPERIMENT, FIX, TEST, SEARCH sequence. This guided process enforces safe, reproducible debugging with documented results.

Can I audit my debugging process for production issues?

Yes, you can audit debugging processes for production issues using a CHECKER path. It outputs a status table highlighting methodology violations and warnings to ensure your root-cause analysis is sound.

What should I do when stuck diagnosing a software defect?

When stuck diagnosing a software defect, use an APPLIER path for guided stabilization, hypothesis formation, and fix-verification. It provides practical checklists to systematically triangulate and resolve problems.

Does scientific debugging work for both development and production environments?

Yes, scientific debugging works across development, QA, and production environments. It handles intermittent failures, crashes, and regressions by enforcing reproducibility and structured process-improvement checklists.