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.
SkillScore96Maintained
Automatic
◆Coding pack
Last verified 8/9/2026
What it changes
Passed 23 of 24 test cases with the skill, and 21 of 24 without it.
Without skill88%
With skill96%
Checks it passed that the model alone missed
Identifies the placeholder TODO comment as an unaddressed failure path.
Recommends reviewing for missing error branches and omitted edge cases.
Points out that inspecting added lines alone misses ungenerated failure paths.
and 1 more in the full report
3 fixed20 passed either way0 still failing1 broke
Pass-rate lift
+8 pp
Tokens
+14%
Agent turns
0%
Response time
-1%
Model gemini-3.6-flashMeasured 8/9/2026v123 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
When reviewing an AI-generated pull request, the reviewer only looked at the added lines in the diff view and verified syntax. What critical review step was missed?
What was checked, without and with the skill
Checked
Without skill
With skill
Points out that inspecting added lines alone misses ungenerated failure paths.
Missed
Passed
Recommends reviewing for missing error branches and omitted edge cases.
Missed
Passed
case-18 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md61 linessingle file
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:
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)