vibe-debug

Systematize software bug investigation with a ledger-based workflow for symptom tracking and hypothesis validation.

2|1|Updated Mar 1, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #verification #software maintenance #bug tracking

Ready to run

npx skills add https://github.com/adhi-jp/minecraft-modding-mcp --skill vibe-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-debug
Source: https://github.com/adhi-jp/minecraft-modding-mcp/tree/main/.agents/skills/vibe-debug
Command: npx skills add https://github.com/adhi-jp/minecraft-modding-mcp --skill vibe-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves ambiguous or recurring bug reports by enforcing a structured, evidence-based debugging workflow that prevents guesswork and ensures fixes are verified against actual runtime state.

Core Features & Use Cases

Structured Debug Ledger: Maintains a rigorous record of symptoms, hypotheses, and proof paths to prevent context loss during complex investigations.
State-Space Analysis: Guides the user to identify abstract dimensions like lifecycle, ordering, and artifact freshness rather than just patching symptoms.
Use Case: When a user reports a feature is still broken after a previous attempt, use this Skill to perform a dirty worktree preflight, analyze the failure in the debug ledger, and verify the fix with a concrete proof path.

Quick Start

Use the vibe-debug skill to investigate the reported regression in the current project by initializing a new debug ledger for the symptom.

Frequently Asked Questions about vibe-debug

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

FAQPage Schema

How do I structure software debugging to prevent recurring regressions?▼

Structured debugging prevents recurring regressions by maintaining a rigorous ledger of symptoms, hypotheses, and proof paths to ensure fixes are verified against actual runtime state.

What is the best way to track root cause analysis for complex state-space bugs?▼

Tracking root cause analysis for complex bugs requires a ledger-based workflow that identifies abstract dimensions like lifecycle, ordering, and artifact freshness rather than just patching symptoms.

How do I verify a bug fix without introducing non-regressive code changes?▼

Verify a bug fix by enforcing proof-based closure criteria and repository history boundaries, ensuring the repair is validated against runtime artifacts and environment-specific behaviors.

How do you troubleshoot a feature still broken after a previous fix attempt?▼

Troubleshoot a still-broken feature by performing a dirty worktree preflight, analyzing the failure in a debug ledger, and verifying the repair with a concrete proof path.

When do I need a ledger-based workflow for bug tracking and software maintenance?▼

You need a ledger-based workflow for bug tracking when resolving ambiguous or recurring bug reports that require evidence-based investigation to prevent context loss during complex state-space analysis.

Does structured troubleshooting work for environment-specific runtime behaviors?▼

Structured troubleshooting works for environment-specific behaviors by operating across complex state-space dimensions, including runtime artifacts and lifecycle events, to ensure verified repairs.