How do I install the AI Debug skill?

Run npx skillmds@latest add arcasilesgroup/ai-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 AI Debug safe to use?

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

Which AI agents work with AI 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 AI Debug free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published AI Debug?

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

AI Debug by arcasilesgroup — Agent Skill

Name: AI Debug
Rating: 4.2 (5 reviews)
Author: arcasilesgroup

AI Debug

Finds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-review. Not for exploring an unfamiliar area — use /ai-explore. Not for designing the fix — once the cause is named, use /ai-plan.

arcasilesgroup 26092b3 2 files · 5.1 KB Updated Sep 10, 2026

File contents

Find the cause, not the symptom

What it produces

A named cause at file:line, a check that fails because of it, and only then a fix.

Steps

Reproduce it. If you cannot reproduce it, say so plainly and stop guessing: the next useful thing is a way to reproduce it, not a change.
Read the failing output in full. The first error is usually the real one and the rest are its consequences; the last error is the one people paste.
Name a cause you can point at. file:line, and one sentence on why that line produces this symptom. "Probably a race" is not a cause. If two causes are plausible, say which observation would tell them apart, then go and make that observation.
Before the fix, write the check that fails for this reason. A fix with no failing check before it is a change with an opinion attached.
Fix the cause, at the place all the callers go through. Patching the one path the report named leaves every sibling caller broken, and the shared fix is usually the smaller diff.
Run the check. Then run the suite. Then say what you changed and why it fixes the cause you named, not the symptom that was reported.
If you are two attempts in and it is still not fixed, stop and say so. That is a rule, not a suggestion: the third attempt is where the guessing starts.

Conflicts

Read both sides for intent before touching either. Lock files and generated files are regenerated, never merged by hand. Migrations are ordered, not combined. If two people meant different things, that is a conversation, not a resolution.

What this is not

"I know what the bug is even though I cannot reproduce it" — a cause you cannot reproduce is a guess: the next useful thing is a way to reproduce it, not a change.

Done when

The cause is named at file:line and a person could disagree with it.
A check exists that fails without the fix and passes with it.
You said what you changed, in a sentence somebody could act on.

---name: ai-debugdescription: Finds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-review. Not for exploring an unfamiliar area — use /ai-explore. Not for designing the fix — once the cause is named, use /ai-plan.license: Apache-2.0---# Find the cause, not the symptom## What it producesA named cause at `file:line`, a check that fails because of it, and only then a fix.## Steps1. Reproduce it. If you cannot reproduce it, say so plainly and stop guessing: the next useful thing is a way to reproduce it, not a change.2. Read the failing output in full. The first error is usually the real one and the rest are its consequences; the last error is the one people paste.3. Name a cause you can point at. `file:line`, and one sentence on why that line produces this symptom. "Probably a race" is not a cause. If two causes are plausible, say which observation would tell them apart, then go and make that observation.4. Before the fix, write the check that fails for this reason. A fix with no failing check before it is a change with an opinion attached.5. Fix the cause, at the place all the callers go through. Patching the one path the report named leaves every sibling caller broken, and the shared fix is usually the smaller diff.6. Run the check. Then run the suite. Then say what you changed and why it fixes the cause you named, not the symptom that was reported.7. If you are two attempts in and it is still not fixed, stop and say so. That is a rule, not a suggestion: the third attempt is where the guessing starts.## ConflictsRead both sides for intent before touching either. Lock files and generated files areregenerated, never merged by hand. Migrations are ordered, not combined. If two peoplemeant different things, that is a conversation, not a resolution.## What this is not- "I know what the bug is even though I cannot reproduce it" — a cause you cannot reproduce is a guess: the next useful thing is a way to reproduce it, not a change.## Done when- The cause is named at `file:line` and a person could disagree with it.- A check exists that fails without the fix and passes with it.- You said what you changed, in a sentence somebody could act on.

Frequently asked questions