technical-debt-hunter
Skill7 starsChanged 6 days agoMITView on GitHub
Find, size, and prioritize technical debt from code, delivery, reliability, security, and developer-experience evidence. Use for repository audits, roadmap planning, slow delivery, incident follow-up, or modernization decisions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- letscooktech-studio/ai-engineering-arsenalword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- letscooktech-studio/ai-engineering-arsenal★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentic-skill-pack-integratorSkill
- ai-agent-architecture-reviewerSkill
- ai-search-optimizerSkill
- competitor-analyzerSkill
- cost-explosion-detectorSkill
- cto-operating-systemSkill
- database-architectSkill
- nextjs-production-architecture-reviewerSkill
- nvidia-accelerated-ai-systems-operatorSkill
- production-ai-saas-builderSkill
- production-risk-labSkill
- security-auditorSkill
- seo-auditorSkill
- startup-validatorSkill
- supabase-production-auditorSkill
- system-architectSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Do not equate style preference with debt.
- Distinctive: line 27
Treat low-confidence findings as investigation tasks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Debt Hunter
Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.
Find debt that changes delivery, reliability, cost, or risk—not merely code that looks old.
Workflow
- Gather evidence: change frequency, defects, incidents, CI duration, dependency age, ownership gaps, duplication, complexity, and developer reports.
- Trace debt to an observable consequence and distinguish root cause from symptom.
- Score impact, urgency, recurrence, remediation cost, and confidence. Group repeated symptoms into debt themes.
- Propose thin slices that create measurable improvement while protecting product delivery.
- Define leading and lagging indicators, ownership, and a stop condition for each initiative.
Output contract
Return a debt register with evidence, impact narrative, score, proposed intervention, estimate range, dependencies, and success metric; plus a 30/60/90-day sequence.
Quality gates
- Do not equate style preference with debt.
- Treat low-confidence findings as investigation tasks.
- Quantify opportunity cost or risk where data permits.
- Recommend deletion or simplification before re-platforming.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.