Stats
Actions
Tags
From devops-skills
Identifies technical debt patterns like duplicated code, inconsistent naming, dead code, TODOs, magic numbers, long functions, and deep nesting. Use for code reviews and refactoring analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devops-skills:techdebt-finderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Identify duplicated code, inconsistent patterns, and refactoring opportunities.
Identify duplicated code, inconsistent patterns, and refactoring opportunities.
| Debt Type | Detection Method |
|---|---|
| Duplicated code | Hash-compare function bodies |
| Similar-but-diff | Fuzzy match on structure |
| Inconsistent naming | Regex for mixed conventions |
| Dead code | Unreferenced exports/functions |
| TODO/FIXME | Grep for comment markers |
| Magic numbers | Literals outside const/config |
| Long functions | Line count > threshold |
| Deep nesting | Indentation level analysis |
## Technical Debt Report
### High Priority (fix soon)
- [DUPLICATE] src/utils/format.ts:23 ↔ src/helpers/fmt.ts:45
Similar: 87% | Impact: High (called 12 places)
### Medium Priority (plan for)
- [INCONSISTENT] Mixed naming: getUserData vs fetch_user
Files: api.ts, service.ts, handler.ts
### Low Priority (track)
- [TODO] 23 TODO comments, oldest: 2023-01-15
npx claudepluginhub spences10/claude-code-toolkit --plugin devops-skillsDetects technical debt using parallel subagents: duplicated code, dead imports, security issues, and complexity hotspots. Run at session end or before commits/merges.
Identifies, categorizes, and prioritizes technical debt across code, architecture, tests, dependencies, docs, and infrastructure. Scores by impact, risk, effort; outputs remediation plans.
Systematically identify, classify, and prioritize technical debt in codebases using SQALE model and Fowler's quadrant. Guides static analysis, debt register creation, and ROI-based remediation.