route-debug

What problem does it solve?

This Skill eliminates inefficient, guesswork-based debugging that leads to repeated failed fixes and missed root causes for code bugs, test failures, and regressions, especially when route-lookup has already identified relevant code files to examine.

Core Features & Use Cases

• Phased Debugging Workflow: Enforces a 3-phase process (reproduce and scope, trace data flow, hypothesize and test) that ensures root causes are identified before any fixes are attempted.
• Leverages Route-Lookup Results: Uses pre-existing route-lookup output to prioritize relevant code files, eliminating redundant time spent locating bug-related code.
• Built-in Guardrails: Includes anti-pattern checks, red flags to stop unproductive debugging, and clear handoff logic to implementation tools to avoid wasted effort.
• Use Case: For example, when a user reports a regression in the payment processing feature after a recent deploy, use this Skill to trace the error from the reported symptom back to the exact divergence point in the code, confirm the root cause, and prepare a structured handoff to the implementation team.

Quick Start

Use the route-debug skill to perform root cause analysis for the reported checkout flow crash, following the phased workflow after reviewing the route-lookup results for relevant payment processing code.