debug

Diagnose and fix bugs through root cause analysis with a hotfix mode for production emergencies.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/natthasath/natthasath-marketplace --skill debug-natthasath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/natthasath/natthasath-marketplace/tree/main/plugins/projects/skills/debug
Command: npx skills add https://github.com/natthasath/natthasath-marketplace --skill debug-natthasath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often leads to superficial patches that treat symptoms instead of causes, or to risky rushed changes during production incidents. This Skill enforces a disciplined root cause analysis workflow for normal bugs and a tightly constrained hotfix procedure for production emergencies. ## Core Features & Use Cases - Root Cause Analysis: Reproduce the bug, gather evidence with Grep and git log, identify the true root cause, and report it before making any fix. - Hotfix Mode (--hotfix): Create a hotfix branch from main, apply a minimal fix under ~50 lines, run only directly related tests, and require user approval of the branch name and commit message before acting. - Test-Driven Fix Verification: Add a test that reproduces the bug (failing before, passing after) and run the project's test command from tech-stack.md after fixing. - Use Case: When a production error alert fires, invoke the skill with "--hotfix payment timeout error" to get a minimal, reviewed fix on a dedicated hotfix branch without touching unrelated code. ## Quick Start Ask the assistant to debug a described bug or error message, optionally adding --hotfix for a production emergency fix.

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 with root cause analysis?▼

Describe the bug, expected behavior, actual behavior, and any error message. The skill reproduces the issue, searches the codebase with Grep, reviews recent git history, identifies the root cause, and reports it before applying a targeted fix with a regression test.

How to apply an emergency hotfix to production code safely?▼

Use the --hotfix flag to create a hotfix/<slug> branch from main, apply a minimal fix under roughly 50 lines, run only directly related tests, and approve the branch name and commit message before anything is committed. Force pushes and unrelated refactors are forbidden.

Does the debug skill run the full test suite after a fix?▼

In normal mode it runs the project's test command defined in tech-stack.md after fixing. In hotfix mode it runs only tests directly related to the fix to keep the emergency change fast and isolated.

What happens if a hotfix requires more than 50 lines of changes?▼

The skill stops and notifies you instead of proceeding. Large fixes indicate the problem is not a minimal hotfix candidate, so it pauses for your decision rather than expanding the change scope.

When should I use normal debug mode instead of hotfix mode?▼

Use normal mode for non-urgent bugs where you can afford careful reproduction, evidence gathering, and root cause analysis. Reserve hotfix mode for production emergencies where speed and minimal codebase impact matter most.