debug

Diagnose runtime errors in apps and CKS components with structured reports.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/cardinalconseils/claude-starter --skill debug-cardinalconseils
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/cardinalconseils/claude-starter/tree/main/skills/debug
Command: npx skills add https://github.com/cardinalconseils/claude-starter --skill debug-cardinalconseils

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified diagnostic capability to trace runtime errors and diagnose issues in apps, CKS skills, and agents.

Core Features & Use Cases

  • App debugging: trace failures, collect context, and generate a structured diagnosis and safe recovery steps.
  • CKS self-debug: diagnose misbehaving skills/agents/commands using lifecycle logs and PRD references to guide fixes.
  • Post-diagnosis workflow: provide evidence-backed reports, and suggest fixes that require user approval before changes.

Quick Start

Describe the issue you're seeing, and the Skill will diagnose the root cause and propose a safe fix plan.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose runtime errors and trace app failures?▼

To diagnose runtime errors, describe the issue you are seeing. The system traces failures, collects runtime context, and generates a structured diagnosis with evidence-backed recovery steps. It enforces language-agnostic instrumentation and requires diagnosing root causes before proposing fixes.

What is the best way to debug misbehaving CKS skills and agents?▼

The best way to debug misbehaving CKS components is using the self-debug workflow. It diagnoses issues by analyzing lifecycle logs and PRD references to guide fixes, producing evidence-backed reports that require your approval before any changes are applied.

Can I use this to fix runtime issues across different programming languages?▼

Yes, you can fix runtime issues across different programming languages. The diagnostic process enforces language-agnostic instrumentation, allowing you to trace failures and collect context uniformly across various apps and CKS components to produce structured diagnoses.

How do I get a structured diagnosis and safe recovery steps for app debugging?▼

To get a structured diagnosis for app debugging, describe the runtime misbehavior. The system traces the failure, collects contextual evidence, and generates a structured diagnosis with safe recovery steps, suggesting fixes that require your approval before implementation.

Does the diagnostic process log evidence for traceability before applying fixes?▼

Yes, the diagnostic process logs evidence for traceability before applying fixes. It requires diagnosing root causes first and provides evidence-backed reports. Any suggested fixes are guided by this evidence and require user approval before changes are made.