# Debug

> Finds root cause of bugs or unexpected behavior. Use for errors, failures, hydration issues, regressions, or when the user says /debug. Proposes a minimal fix; asks before implementing unless the user already asked to fix it.

- Skill: `axidify/debug` (Agent Skill)
- Install (CLI): `npx skillmds@latest add axidify/debug`
- Raw SKILL.md: https://api.skillmd.com/api/skills/axidify/debug/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Axidify (https://skillmd.com/u/axidify)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/axidify/debug

---


# Debug

**Not this skill:** building a known feature or applying an approved plan →
**implement**. If the user is in **Cursor Debug mode**, follow that mode;
otherwise use this checklist.

## Checklist

1. **Symptoms** — errors, logs, repro steps, expected vs actual
2. **Repro matrix** — browser/OS, data state, auth role, feature flags when relevant
3. **Trace** — follow the path from trigger to failure
4. **Layer** — UI, client state, server/API, data store, config, external service
5. **Pinpoint** — root cause with file + function (and line when useful)
6. **Fix proposal** — smallest change that fixes the cause, not symptoms only
7. **Implement** — only if the user asked to fix, or after they approve

## Rules

- Prefer evidence (stack traces, failing tests) over guesses
- Use `git bisect` or commit range when user gives a regression window
- For backend: check logs, request/response, DB queries, env/config before patching
- Do not change unrelated code “while you’re here”
- If not reproducible, state what you tried and what remains **unknown**

After root cause is known and the user wants the fix built, continue with
**implement**.

## Related skills

- **test** — reproduce via failing tests
- **ui-browser-check** — UI-layer symptoms in a running app
- **ci** — failure only on CI