skills.rest
joshft
joshftCOMMUNITY
Explore all skills by this author →
GitHub

cdebug

Debug codebases through structured phases with artifacts output to .correctless/artifacts/.

65|2|Updated Mar 27, 2026
Search Tags:#tdd#debugging#multi-agent#bug-investigation#team-workflow#artifact-output
One-click install
npx skills add https://github.com/joshft/correctless --skill cdebug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cdebug
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cdebug
Command: npx skills add https://github.com/joshft/correctless --skill cdebug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, multi-agent approach to debugging that ensures root-cause analysis, hypothesis-driven testing, and test-driven fixes instead of patching symptoms.

Core Features & Use Cases

  • Structured phases: reproduction, root-cause investigation, hypothesis testing, fix, and verification with clear handoffs between agents.
  • Progress visibility and traceability: mandatory status updates and artifacts to track each phase and decision.
  • Artifact-driven: outputs investigation results and postmortems to .correctless/artifacts/ for future reference.
  • Escalation path: after three failed hypotheses, escalates to an architectural review.

Quick Start

Invoke the /cdebug workflow on a bug area and follow the guided phases to reproduce, hypothesize, and verify a fix.

Frequently Asked Questions about cdebug

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

FAQPage Schema
How do I debug complex codebases using a structured bug investigation workflow?▼

A structured bug investigation workflow guides you through reproduction, root-cause analysis, hypothesis testing, and verification phases to debug complex codebases, ensuring disciplined root-cause resolution instead of symptom patching.

What is test-driven debugging and how does it apply hypotheses to bug fixes?▼

Test-driven debugging applies hypotheses to bug fixes by enforcing a structured workflow where you test reproducible steps and validate root-cause theories before applying fixes, ensuring traceability through artifact outputs.

Does multi-agent debugging enforce phase boundaries and progress visibility for bug resolution?▼

Multi-agent debugging enforces progress visibility and phase boundaries for bug resolution by separating agents across reproduction, investigation, and verification, mandating status updates and artifact outputs for each phase.

What is the best way to track bug investigation artifacts and postmortems for future reference?▼

The best way to track bug investigation artifacts and postmortems is outputting them to a dedicated directory like .correctless/artifacts/, ensuring progress visibility, traceability, and structured handoffs between debugging phases for future reference.

When should I escalate a bug investigation to an architectural review?▼

You should escalate a bug investigation to an architectural review after three failed hypotheses, triggering a higher-level structural assessment to resolve the root cause when standard reproduction and testing phases do not yield a fix.

Why does my debugging workflow result in symptom patching instead of root-cause resolution?▼

Debugging workflows result in symptom patching instead of root-cause resolution when they lack a structured, hypothesis-driven approach with clear phase boundaries, test-driven fixes, and mandatory artifact outputs for thorough bug investigation.

Related Skills

Explore More Software Engineering Skills→
drhazemibclcdrhazemibclc

bug-reproduction-validator

Analyze bug reports to reproduce issues and classify them as bugs, user errors, or environmental problems.

Community
Advanced
special-place-administratorspecial-place-administrator

postmortem

Analyze campaign artifacts and git history to generate structured postmortem reports.

Community
Advanced
jasonwilmotjasonwilmot

debug

Coordinate a structured debugging workflow to reproduce and resolve software bugs.

Community
Intermediate
SatoryKonoSatoryKono
1

agent-orchestration

Coordinate BioETL multi-agent workflows across py-* profiles using an orchestration map.

Community
Intermediate