debug-issue

Diagnoses root causes by reproducing failures and tracing them upstream.

3|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/nuttaruj/rolepod --skill debug-issue-nuttaruj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/nuttaruj/rolepod/tree/main/core/skills/debug-issue
Command: npx skills add https://github.com/nuttaruj/rolepod --skill debug-issue-nuttaruj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you debug broken software systematically instead of guessing. It is designed for situations where tests start failing, builds break, output is wrong, regressions return, or a recent change introduced an unfamiliar error.

Core Features & Use Cases

  • Disciplined root-cause analysis: Enforces a reproduce → trace upstream → failing test → minimal fix workflow so fixes address the source of the bug rather than hiding the symptom.
  • Safer debugging decisions: Adds guardrails such as rollback-first behavior, one-hypothesis-at-a-time investigation, hard stops after repeated failed attempts, and escalation guidance for flakes or multi-component failures.
  • Structured debugging artifacts: Provides reusable templates for a debug report and a hypothesis ledger, plus references for root-cause tracing and intermittent test triage.
  • Use cases: Debug a regression introduced by a recent commit, isolate a flaky test caused by shared state, trace a UI failure through browser evidence, or identify which layer is failing in a cross-service system.

Quick Start

Ask the AI to use the debug-issue skill to reproduce the failure with one deterministic command, trace the bug upstream to its root cause, write a failing regression test, and apply the smallest safe fix.

Frequently Asked Questions about debug-issue

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

FAQPage Schema
How do I find the root cause of a software regression instead of just fixing the symptom?

To find the root cause of a software regression, you need to reproduce the failure deterministically, trace symptoms upstream, capture the bug in a failing test, and apply a minimal regression-safe fix.

What is the best way to debug a flaky test caused by shared state?

Debugging a flaky test requires deterministic reproduction and upstream boundary tracing. If reproduction fails, the process mandates escalating the issue rather than continuing to guess at the intermittent test failure.

How do I debug a multi-component system failure across different services?

To debug a multi-component system failure, trace symptoms upstream to identify which layer is failing. You must maintain one-hypothesis-at-a-time investigation and verify the full test surface before handoff.

When should I rollback a recent commit during debugging?

You should rollback a recent commit during debugging when the timing of the failure matches the change. Rollback-first reasoning is required to quickly determine if a recent commit introduced the broken behavior.

What should I do if I cannot reproduce a broken software build or test failure?

If you cannot reproduce a broken software build or test failure, you must enforce a hard stop after repeated failed attempts. The debugging process provides escalation guidance for flakes or multi-component failures when deterministic reproduction fails.