skills.rest
c-daly
c-dalyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Automates structured software debugging from triage to verified fixes.

Updated Jan 4, 2026
Search Tags:#automation#workflow#debugging#triage#phases#root-cause#ci
One-click install
npx skills add https://github.com/c-daly/agent-swarm --skill debug-c-daly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/c-daly/agent-swarm/tree/main/skills/debug
Command: npx skills add https://github.com/c-daly/agent-swarm --skill debug-c-daly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The debug workflow provides a structured, repeatable process for diagnosing and solving bugs by verifying root cause before implementing fixes.

Core Features & Use Cases

  • End-to-end debugging lifecycle from triage to done, including adversary gates to prevent premature fixes.
  • Scripted commands and phase guards to ensure changes are proven before coding.
  • Guidance for collaborative debugging, pushing validated changes, and status checks.

Quick Start

Start a debugging workflow session with a bug description, then follow the guided phases: python3 lib/debug_workflow.py start "<your bug description>"

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a bug systematically from triage to fix?▼

Structured debugging automates a guided workflow across triage, reproduction, hypothesis formation, proof, fix, and verification phases. Start with `python3 lib/debug_workflow.py start "<bug description>"` to follow phase gates that enforce root-cause validation before coding, preventing premature fixes.

What's the best way to ensure root cause is identified before implementing a fix?▼

Root-cause debugging enforces phase guards and state persistence to verify the underlying problem before changes are written. The workflow guides evidence gathering and hypothesis formation, then validates fixes against adversary gates to confirm the issue is actually resolved.

Can I automate debugging workflows across CI and deployment pipelines?▼

Yes. The workflow integrates status checks and adversary gates into CI pipelines to prevent unproven fixes from reaching production. Scripted commands and phase enforcement ensure changes are validated and pushed only after root cause is confirmed.

How does collaborative debugging work in a team environment?▼

The structured workflow provides repeatable phases and state persistence, enabling teams to hand off debugging work with full context. Phase guards and documented evidence gathering create a shared reference for collaborative root-cause analysis and fix validation.

What happens if I try to skip phases or push changes without proof?▼

Phase guards prevent advancement without completing triage, reproduction, and proof stages. Adversary gates block premature pushes, enforcing that root cause is validated and fixes are proven effective before deployment.

Related Skills

Explore More Software Engineering Skills→
cslsoftwarescslsoftwares

quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Community
Intermediate
ByronWilliamsCPAByronWilliamsCPA

Code Quality Skill

Validate Git workflows with conventional commits and repository health checks.

Official
Intermediate
muklesmukles

reproduce-bug

Automate bug reproduction and investigation workflows from GitHub issues.

Community
Advanced
rsmdtrsmdt
381

debugging-methodology

Guide hypothesis-driven debugging with evidence-based root-cause analysis.

Community
Advanced