skills.rest
try-works
try-worksCOMMUNITY
Explore all skills by this author →
Website𝕏@trydotworksGitHub

recursive-debugging

Analyze bugs and failing tests to produce a Phase 1.5 root-cause summary.

128|10|Updated Apr 6, 2026
Search Tags:#debugging#reproducibility#root-cause-analysis#bug-fix#debug-workflow#phase-1.5
One-click install
npx skills add https://github.com/try-works/recursive-mode --skill recursive-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recursive-debugging
Source: https://github.com/try-works/recursive-mode/tree/main/skills/recursive-debugging
Command: npx skills add https://github.com/try-works/recursive-mode --skill recursive-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic root-cause debugging prevents wasted effort by avoiding quick fixes and ensures fixes address the real problem in recursive-mode.

Core Features & Use Cases

  • Phase 1.5 root-cause insertion between Phase 1 and Phase 2 to structure debugging
  • Artifact-driven analysis including error analysis, reproduction verification, and evidence gathering
  • Clear root-cause summaries and test-fix planning that feed Phase 2

Quick Start

Invoke Phase 1.5 Root Cause Analysis to document the root cause, lock Phase 1, and prepare Phase 2 plans.

Frequently Asked Questions about recursive-debugging

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

FAQPage Schema
What is root-cause debugging and when do I need it for bug fixes?▼

Root-cause debugging identifies the underlying cause of bugs or unexpected behavior to prevent wasted effort on quick fixes. You need it when facing failing tests or integration issues that require systematic error analysis before applying a fix.

How do I perform root-cause analysis before fixing failing tests?▼

To perform root-cause analysis, document the error, verify reproduction, gather evidence, and summarize the conclusive root cause. This creates an artifact that gates advancement to the fix phase, ensuring the real problem is addressed.

What's the best way to structure a debug workflow for integration issues?▼

The best way to structure a debug workflow is inserting a root-cause analysis phase between initial planning and implementation. This artifact-driven approach locks requirements, verifies reproduction, and prepares test-fix plans before applying solutions.

Why does my bug fix keep failing when I skip root-cause analysis?▼

Bug fixes fail when skipping root-cause analysis because quick fixes address symptoms rather than the underlying cause. Without evidence gathering and reproduction verification, the original bug or unexpected behavior persists across integration requirements.

Can I use root-cause debugging for reproducibility verification in my workflow?▼

Yes, root-cause debugging includes reproduction verification as a core component. It confirms the bug's reproducibility, gathers supporting evidence, and produces a conclusive summary that feeds directly into your downstream test-fix planning.

Does recursive-debugging require any specific dependencies or components?▼

No, recursive-debugging requires no external dependencies or components. It operates as a standalone workflow phase, generating an error analysis artifact that locks prior planning and gates advancement to subsequent implementation phases.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
sachio222sachio222

systematic-debugging

Enforce root-cause investigation before implementing fixes for software issues.

Community
Advanced
try-workstry-works
128

recursive-tdd

Enforce RED-GREEN-REFACTOR TDD cycles with mandatory Phase 3 artifacts.

Community
Advanced
try-workstry-works
4

rlm-debugging

Perform systematic root-cause analysis for RLM bug-fix and failing-test requirements.

Community
Advanced