skills.rest
ngochuy13
ngochuy13COMMUNITY
Explore all skills by this author →
GitHub

debug

N/A

Updated Apr 23, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#logging#incident response#deploy regression#test prevention
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill debug-ngochuy13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/debug
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill debug-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging often stalls when a bug is intermittent, only appears in certain environments, or the root cause is unclear; this Skill helps you systematically narrow down the issue and produce a reliable fix.

Core Features & Use Cases

  • Structured workflow: Reproduce, isolate, diagnose, then fix using a clear step-by-step approach.
  • Evidence-driven troubleshooting: Focus on expected vs. actual behavior, recent changes, logs, and hypotheses to find the real cause.
  • Actionable outputs: Produce a Debug Report template that captures reproduction steps, root cause, fix details, and prevention actions.
  • Use Case: When something breaks after a deploy or only happens in production, you can collect the exact error message, isolate the divergent path, and document the corrective change plus regression tests.

Quick Start

Tell the Skill the exact error message and what changed recently, then request a structured Debug Report with reproduction, root cause, fix, and prevention steps.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I systematically isolate a production-only regression?▼

Structured troubleshooting isolates post-deploy regressions by gathering the exact error message, comparing expected versus actual behavior, analyzing recent changes, and testing hypotheses to identify the root cause.

What is the best way to document a root cause analysis for incident response?▼

Root cause analysis documentation should capture reproduction steps, the isolated underlying cause, specific fix details, and prevention actions including regression tests to ensure the incident does not recur.

How do I troubleshoot an intermittent software failure when the root cause is unclear?▼

Troubleshooting intermittent software failures requires an evidence-driven approach: collecting exact error messages, defining reproduction steps, and iteratively testing hypotheses against recent environmental changes.

What information do I need to provide before starting a debugging workflow?▼

Before starting the debugging workflow, you must provide the exact error message, expected versus actual behavior, detailed reproduction steps, and relevant context regarding recent changes to guide hypothesis testing.

How can I prevent behavior divergence from causing future test failures?▼

To prevent behavior divergence and future test failures, you implement regression tests specifically designed to validate the corrected behavior path and document prevention actions within a structured debug report.

Related Skills

Explore More Software Engineering Skills→
pcasarettopcasaretto

bug-reproduction-validator

Reproduce reported software issues and classify them as bugs, environmental problems, or user errors.

Community
Advanced
Xeron2000Xeron2000
371

trellis-break-loop

Analyze recurring bugs with a structured root-cause classification framework.

Community
Advanced
dhntdhnt

rollback

Coordinate deployment rollback with pre-flight checks and health verification.

Official
Intermediate
rabbicserabbicse

debugging-wizard

Analyze errors, stack traces, and logs to isolate software failure root causes.

Community
Advanced