No No Debug — AI skill for Claude Code

no-no-debug

A self-evolution system for AI coding assistants

**v1.3.0 — periodic review now actually works.** Earlier versions promised "auto-triggers every 3 days" but had no enforcement mechanism — the review only ran when manually invoked, and the tracker went stale silently. v1.3.0 ships `hooks/review_reminder.py`, a `UserPromptSubmit` hook that checks the tracker on each message and reminds the AI to run the review when it's overdue. See [CHANGELOG.md](./CHANGELOG.md) for the one-step migration from v1.2.0.

What problem does this solve?

10 minutes writing code, 2 hours debugging.

This skill fills the gap in AI's cross-session error memory, delivering three things:

1. Dramatically less debug time
2. Higher code quality
3. A self-evolution feedback loop

The longer you use it, the fewer mistakes get repeated.

How it works

1. Real-time Logging (automatic)

When the AI is corrected, code errors occur, deploys fail, or tests don't pass — it automatically appends to a local error_log.md with a timestamp. No need to say "write that down."

2. Three Gates (on every code change)

Before the change: what does this affect? After the change: did you actually verify it? Before deploying: did you test with a non-admin account?

Runs silently. No output when all gates pass.

3. Periodic Review (auto-triggers every 3 days)

Reads error_log.md, categorizes by dimension, updates error_tracker.md, outputs an evolution report. Review frequency is configurable: 1 day / 3 days (default) / 7 days.

4. Rule Accumulation

New error type → automatically creates a prevention rule. Repeated offense → counter increments, rule strengthens. 4 consecutive clean periods → marked as cured.

Rules persist across sessions — nothing gets lost.

5. Confirmation Gate

The following situations require user confirmation before proceeding:

• New feature development (not a bug fix)
• Changes involving databases, environments, or deployments
• Publishing to ex