How do I install the Hyper Debug skill?

Run npx skillmds@latest add zeikar/hyper-debug in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hyper Debug safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hyper Debug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hyper Debug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hyper Debug?

zeikar (@zeikar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hyper Debug by zeikar — Agent Skill

Name: Hyper Debug
Author: zeikar

Hyper Debug

Use when encountering a test failure, exception, regression, or unexpected behavior — before proposing fixes. Also when the user invokes /hyperclaude:hyper-debug. Forms hypotheses systematically instead of guess-and-check thrashing.

zeikar 552838c 2.0 KB Updated Sep 17, 2026

File contents

hyper-debug

Debugging discipline tailored to this author's preferences.

Skip when

You already know the exact line and exact fix (typo, missing import, obvious null check). Just fix it.
The "bug" is a one-character correction that doesn't merit a hypothesis.

If you catch yourself rationalizing ("the cause is probably X, let me just try…") — that's hypothesis stacking. Run the cycle.

The cycle

Reproduce. Smallest possible repro. If you can't reproduce, you can't debug.
State the expected vs actual. Two sentences. "I expected X. I got Y."
Hypothesize one cause. One. Not five. Pick the most likely.
Predict what would prove the hypothesis right or wrong before running anything. "If hypothesis is correct, X should happen."
Run the experiment. Compare to prediction.
If wrong, hypothesize again. New hypothesis. Don't stack them.
Once cause is confirmed, write a failing test that captures the bug before fixing — so it doesn't regress silently later.
Fix. Run. Commit.

Anti-patterns

Hypothesis stacking — trying five "fixes" at once and not knowing which one worked.
Skipping the regression test — "the fix is obvious, no test needed." Write the test.
Logging-only debugging — endless console.log without forming hypotheses. Logs serve a hypothesis, not the other way around.
Reading code top-to-bottom — start at the failing assertion and walk backward, not forward.

When to escalate

If after 2-3 hypotheses you still don't know the cause, stop iterating. Re-read the error message slowly, check if your repro is actually exercising the buggy code, or take a 5-minute break — you have a wrong assumption somewhere upstream.

---name: hyper-debugdescription: Use when encountering a test failure, exception, regression, or unexpected behavior — before proposing fixes. Also when the user invokes /hyperclaude:hyper-debug. Forms hypotheses systematically instead of guess-and-check thrashing.---# hyper-debugDebugging discipline tailored to this author's preferences.## Skip when- You already know the exact line and exact fix (typo, missing import, obvious null check). Just fix it.- The "bug" is a one-character correction that doesn't merit a hypothesis.If you catch yourself rationalizing ("the cause is probably X, let me just try…") — that's hypothesis stacking. Run the cycle.## The cycle1. **Reproduce.** Smallest possible repro. If you can't reproduce, you can't debug.2. **State the expected vs actual.** Two sentences. "I expected X. I got Y."3. **Hypothesize one cause.** One. Not five. Pick the most likely.4. **Predict what would prove the hypothesis right or wrong** before running anything. "If hypothesis is correct, X should happen."5. **Run the experiment.** Compare to prediction.6. **If wrong, hypothesize again.** New hypothesis. Don't stack them.7. **Once cause is confirmed, write a failing test that captures the bug** before fixing — so it doesn't regress silently later.8. **Fix. Run. Commit.**## Anti-patterns- **Hypothesis stacking** — trying five "fixes" at once and not knowing which one worked.- **Skipping the regression test** — "the fix is obvious, no test needed." Write the test.- **Logging-only debugging** — endless `console.log` without forming hypotheses. Logs serve a hypothesis, not the other way around.- **Reading code top-to-bottom** — start at the failing assertion and walk backward, not forward.## When to escalateIf after 2-3 hypotheses you still don't know the cause, stop iterating. Re-read the error message slowly, check if your repro is actually exercising the buggy code, or take a 5-minute break — you have a wrong assumption somewhere upstream.

Frequently asked questions