debug

Identifies and fixes bugs using a structured workflow with triage, RCA, and fix tracks.

33|Updated Jan 5, 2026

Search Tags:#workflow #debug #state-management #hotfix #root-cause-analysis #thorough

Ready to run

npx skills add https://github.com/lvlup-sw/exarchos --skill debug-lvlup-sw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/debug
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill debug-lvlup-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bug investigation and fix workflows are often lost across sessions and context windows. Exarchos provides a deterministic, auditable process that surfaces triage, investigation, RCA, and hotfix/thorough tracks with guardrails and state persistence.

Core Features & Use Cases

Structured triage to assess symptoms, urgency, and affected areas.
Dual-track workflow (hotfix for rapid fixes and thorough for RCA-driven fixes) with explicit phase gates.
Persistent state and references to keep context across sessions.

Quick Start

Activate the debug skill by describing a bug to begin triage and let the system select the appropriate track.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I maintain debug workflow state and context across multiple sessions?▼

To maintain debug state across sessions, use a structured workflow with state persistence and references. This preserves triage, investigation, and RCA context across context windows, ensuring reproducible fixes when resuming work.

What is the difference between a hotfix and a thorough track in bug investigation?▼

In bug investigation, a hotfix track provides rapid fixes for immediate issues, while a thorough track delivers RCA-driven fixes. Both tracks use explicit phase gates to enforce deterministic steps, guardrails, and traceability for proper documentation.

How do I start structured triage to assess symptoms and urgency for a bug?▼

Start structured triage by describing the bug symptoms to the system. It will assess symptoms, urgency, and affected areas, then automatically select the appropriate hotfix or thorough track with formal gates to guide the investigation.

When do I need root cause analysis documentation for a software bug fix?▼

Root cause analysis documentation is needed when choosing a thorough track for bug fixes. Structured debug workflows enforce traceability and RCA documentation to ensure deterministic, reproducible fixes rather than just patching symptoms.

Does a structured debugging workflow support guardrails for reproducible fixes?▼

Yes, a structured debugging workflow enforces deterministic steps and guardrails to ensure reproducible fixes. It uses formal phase gates and state persistence to maintain context and traceability throughout triage, investigation, and implementation.