hello-debug

Diagnose bugs through root-cause analysis, feedback loops, and a four-phase debugging workflow.

702|99|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill hello-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hello-debug
Source: https://github.com/hellowind777/helloagents/tree/main/skills/hello-debug
Command: npx skills add https://github.com/hellowind777/helloagents --skill hello-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging often devolves into guesswork: fixes applied without root-cause analysis, repeated failed attempts, and leftover debug logs polluting the codebase. This Skill enforces a disciplined debugging methodology so bugs are reproduced, isolated, and fixed at the root cause rather than patched at the symptom level.

Core Features & Use Cases

  • Feedback Loop First: Requires a reproducible failing test, HTTP script, CLI replay, or minimal verification script before any code change, ensuring the fix can be proven to work.
  • Four-Phase Method: Structured locate, analyze, hypothesize, and fix stages with falsifiable hypotheses and single-variable testing.
  • Git History as Memory: Checks recent commits and past reverted fixes to avoid repeating previously failed approaches.
  • Escalation Ladder: After repeated failures, progressively escalates from reflection to architecture review to user consultation instead of endless blind retries.
  • Use Case: A test suite fails intermittently in CI. The Skill guides the agent to reproduce the failure locally, trace the data flow, form ranked hypotheses, write a failing test, apply a minimal root-cause fix, and clean up all temporary debug logs before delivery.

Quick Start

Ask the agent to debug the failing test or unexpected behavior using the hello-debug workflow, starting with a reproducible feedback loop.

Frequently Asked Questions about hello-debug

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

FAQPage Schema
How do I debug a bug that only happens intermittently?

Increase the reproduction rate first by recording trigger counts, failure ratios, and key conditions. Build a fast feedback loop such as a stress loop or replay script that proves the problem appears and disappears before attempting any fix.

What is root cause analysis in debugging?

Root cause analysis means tracing the error back through the data flow to the underlying defect rather than patching the visible symptom. This Skill requires forming three to five falsifiable hypotheses and testing one variable at a time before fixing.

How should I use git history when debugging?

Run git log to review recent changes and search for past reverted fixes before starting. If a similar fix was already tried and rolled back, avoid repeating that direction and investigate alternative hypotheses.

What should I do when a bug fix keeps failing?

Follow the escalation ladder: after three failures, question whether it is an architecture problem; after four, re-read all related files and git history; after five, stop and present options to the user such as reversing direction or refactoring.

How do I clean up temporary debug logging after fixing a bug?

Tag every temporary log with a unique prefix like [DEBUG-a4f2] when adding it. Before delivery, search for that prefix and remove all temporary logs, verification scripts, and experiment files, or move them to a dedicated debug directory with justification.