/ai-debt-detector
Use after generating code, after accepting AI suggestions, or when reviewing AI-written modules. Also use when code works but feels brittle, when error handling seems thin, when orphaned resources or missing cleanup are suspected, or when the agent claims done but hidden debt
One skill from wshobson-agents.
shell
$ npx -y skills add wshobson/agents --skill ai-debt-detector --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ai-debt-detector
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use after generating code, after accepting AI suggestions, or when reviewing AI-written modules. Also use when code works but feels brittle, when error handling seems thin, when orphaned resources or missing cleanup are suspected, or when the agent claims done but hidden debt
Stats
Stars38,171
Forks4,092
LanguagePython
LicenseMIT
Ships with wshobson-agents
SKILL.md
ai-debt-detector.SKILL.md
--- name: ai-debt-detector description: >- Use after generating code, after accepting AI suggestions, or when reviewing AI-written modules. Also use when code works but feels brittle, when error handling seems thin, when orphaned resources or missing cleanup are suspected, or when the agent claims done but hidden debt may exist. Catches the specific failure patterns AI agents produce that humans would not. --- # AI Debt Detector ## Overview AI agents generate code that passes the happy path but hides debt: missing error handling, orphaned resources, ignored failure modes, hallucinated packages, silent architectural drift. This skill forces a targeted audit for the exact patterns AI agents get wrong. ## When to Use - After any AI code generation session (20+ lines produced) - Before merging AI-generated PRs - When code works but something feels off - After vibe-coding sprints where debt accumulates fastest - When the agent claims done without showing verification ## Process After code generation, scan for these AI-specific debt patterns: 1. **FAILURE MODES** - What happens when this fails? - Network timeout? Disk full? Permission denied? Null input? - Is there a try/catch? Does it catch SPECIFIC errors or swallow everything?
