Technical debt detection and remediation. Run at session end to find duplicated code, dead imports, security issues, and complexity hotspots. Triggers: 'find tech debt', 'scan for issues', 'check code quality', 'wrap up session', 'ready to commit', 'before merge', 'code review prep'. Always uses parallel subagents for fast analysis.
74
63%
Does it follow best practices?
Impact
87%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/techdebt/SKILL.mdSecurity vulnerability classification and report format
Report header: Debt Score
0%
100%
Report header: Scope
100%
100%
Summary table present
100%
100%
Critical Issues section
25%
100%
Hardcoded secret as P0
0%
100%
SQL injection as P0
100%
100%
Insecure crypto as P0
0%
0%
Python-specific: yaml.load
100%
100%
eval/exec as P1
0%
0%
File:line format
0%
100%
Impact field per finding
100%
100%
Fix field per finding
100%
100%
Recommendations section
100%
100%
Complexity/duplication thresholds and summary report structure
Summary table: 4 categories
50%
100%
Debt Score present
0%
100%
Complexity P1 threshold
0%
100%
Function length P1 threshold
0%
100%
Duplication P1 classification
100%
100%
Duplication P2 classification
0%
87%
Dead code: unused imports
50%
100%
File:line location format
25%
100%
Findings grouped by file
25%
50%
Refactoring suggestion for complexity
75%
100%
High Priority (P1) section
100%
100%
Recommendations section
100%
100%
Dead code safe removal criteria and auto-fix safety rules
Dead imports as safe-fix
100%
100%
Security NOT auto-fixable
100%
50%
Complexity NOT auto-fixable
100%
0%
Safe removal: no external refs
100%
100%
Safe removal: not public API
80%
70%
Orphaned function detected
100%
100%
Unreachable code detected
100%
100%
Findings grouped by file
100%
100%
File:line location format
100%
100%
Impact field present
100%
100%
Fix field present
100%
100%
Recommendations section
100%
100%
f772de4
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.