← ClaudeAtlas

ai-debt-detectorlisted

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 you notice orphaned resources or missing cleanup, or when the agent says "done" but you suspect hidden debt. Catches the specific failure patterns AI agents produce that humans wouldn't.
Adit-Jain-srm/skill-forge · ★ 1 · AI & Automation · score 74
Install: claude install-skill Adit-Jain-srm/skill-forge
## 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 (agent wrote 20+ lines) - Before merging AI-generated PRs - When code "works" but something feels off - After vibe-coding sprints — debt accumulates fastest here - When you find yourself saying "the agent said it's done" ## Process After ANY 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? - Are resources cleaned up on failure? (streams closed, connections returned, temp files deleted) 2. ORPHANS — What gets created but never cleaned up? - Temp files, event listeners, intervals, subscriptions, connections - Are there corresponding cleanup/dispose/close calls for every open/create? - In React: does every addEventListener have a removeEventListener in cleanup? 3. EDGE CASES — What inputs break this? - Empty array/string? null/undefined? Very large input? Unicode? Concurrent calls? - Does the code assume the happy path? (hint: AI almost always does) 4. HALLUCINATED DEPS — Do all imports actually exist? - Is every package i