ce-debug

Diagnose and fix bugs through a structured debugging lifecycle from triage to handoff.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill ce-debug-vitallium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-debug
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-debug-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically diagnose and fix bugs using a structured debugging framework that guides users through a repeatable, evidence-based process from issue discovery to resolution.

Core Features & Use Cases

  • End-to-end debugging lifecycle: triage, investigation, root-cause analysis, fixes, and handoff, ensuring reproducible results.
  • Hypothesis-driven analysis with concrete observations, predictions, and smart escalation to manage uncertainty.
  • Reference-rich context: leverages optional references to deepen understanding without forcing code edits.

Quick Start

Describe the bug and reproduction steps, then activate Phase 1 to begin investigation.

Frequently Asked Questions about ce-debug

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

FAQPage Schema
How do I systematically debug a codebase issue from an error trace?

Systematic debugging of a codebase issue uses a structured framework spanning Phase 0 Triage to Phase 4 Handoff, guiding you through hypothesis-driven investigation and root-cause analysis based on error traces.

What is the best way to reproduce a test failure found in a CI pipeline?

Reproducing a test failure in a CI pipeline requires following a disciplined investigation lifecycle that moves from triage to root-cause analysis, ensuring you track concrete observations and predictions.

How does hypothesis-driven investigation work for finding a root cause?

Hypothesis-driven investigation works by forming concrete predictions from observations, testing them to build a causal-chain, and using smart escalation to manage uncertainty until the root cause is found.

Can I use this structured debugging framework for issue-tracker reproductions?

Yes, you can use this structured debugging framework for issue-tracker reproductions by describing the bug and reproduction steps, then activating the investigation phase to begin root-cause analysis.

Do I need to provide code edits to perform a root-cause analysis?

No, you do not need to provide code edits to perform root-cause analysis; the process leverages optional references to deepen understanding and guide the investigation without forcing immediate code modifications.