Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
travisjneuman avatar

Tech Debt Analyzer

  • 115 installs
  • 86 repo stars
  • Updated July 17, 2026
  • travisjneuman/.claude

Helps with ai & agent building tasks during AI-assisted development.

About

tech-debt-analyzer is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • tech-debt-analyzer
  • AI & Agent Building
  • AI-coding skill

Tech Debt Analyzer by the numbers

  • 115 all-time installs (skills.sh)
  • +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #3,917 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/travisjneuman/.claude --skill tech-debt-analyzer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs115
repo stars86
Last updatedJuly 17, 2026
Repositorytravisjneuman/.claude

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

Technical Debt Analyzer

Systematically identify, analyze, and document technical debt.

When to Use

Use for:

  • Analyzing code quality issues
  • Creating technical debt registers
  • Assessing code maintainability
  • Identifying dependency problems
  • Documenting security vulnerabilities
  • Planning refactoring efforts

Don't use when:

  • Writing new code → use generic-feature-developer
  • Code review → use generic-code-reviewer
  • Writing tests → use test-specialist

Quick Analysis Commands

# Find large files (>500 lines)
find src -name "*.ts" -exec wc -l {} + | awk '$1 > 500' | sort -rn

# Find TODO/FIXME markers
grep -rn "TODO\|FIXME\|HACK\|XXX" src/

# Check for console.log in production code
grep -rn "console.log" src/ --include="*.ts" --include="*.tsx"

# Find TypeScript 'any' usage
grep -rn ": any" src/ --include="*.ts" --include="*.tsx"

# Check outdated dependencies
npm outdated

# Security vulnerabilities
npm audit

# Unused exports (requires ts-unused-exports)
npx ts-unused-exports tsconfig.json

Debt Categories

CategoryExamples
Code QualityLarge files, complex functions, TODO/FIXME markers
ArchitecturalTight coupling, missing abstractions, circular deps
TestMissing coverage, fragile tests, slow execution
DocumentationMissing README, outdated docs, no ADRs
DependencyOutdated packages, security vulnerabilities
PerformanceN+1 queries, memory leaks, large bundles
SecurityMissing validation, exposed secrets, XSS/SQL injection

Analysis Workflow

1. Automated Detection

Code Smells to Check:

  • Large files (>500 lines)
  • Complex functions (cyclomatic complexity >10)
  • Debt markers (TODO, FIXME, HACK, XXX)
  • Console statements in production code
  • any types in TypeScript
  • Long parameter lists (>5 params)
  • Deep nesting (>4 levels)

Dependency Issues:

  • Deprecated packages
  • Duplicate functionality
  • Loose version constraints
  • Known vulnerabilities

2. Severity Assessment

SeverityCriteriaAction
CriticalSecurity vulns, data loss riskImmediate fix
HighPerformance problems, blocking issuesCurrent sprint
MediumCode quality, missing docsThis quarter
LowMinor smells, optimizationsWhen convenient

3. Priority Matrix

Impact / EffortLowMediumHigh
High ImpactDo FirstDo SecondPlan & Do
Medium ImpactDo SecondPlan & DoConsider
Low ImpactQuick WinConsiderAvoid

Debt Register Format

## DEBT-001: Description

**Category:** Code Quality | **Severity:** High
**Location:** src/services/UserService.ts

**Description:** Brief description of the issue

**Impact:**

- Business: How it affects delivery
- Technical: Why it's problematic
- Risk: What could go wrong

**Proposed Solution:** What to do about it
**Effort:** Days/hours estimate
**Target:** Sprint/quarter

Prevention Strategies

Automated Guards

{
  "rules": {
    "complexity": ["error", 10],
    "max-lines-per-function": ["error", 50],
    "max-params": ["error", 5],
    "max-depth": ["error", 4]
  }
}

Maintenance Schedule

FrequencyTasks
WeeklyReview TODO/FIXME, update register
MonthlyDependency updates, debt review
QuarterlyFull analysis, architecture review

Self-Critique Checklist

After completing debt analysis:

  • [ ] All automated checks run
  • [ ] Manual review of critical paths done
  • [ ] Severity assessments justified
  • [ ] Proposed solutions are actionable
  • [ ] Priority matrix applied consistently
  • [ ] Register entries are complete

See Also

  • Code Review Standards - Quality checks
  • Project CLAUDE.md - Workflow rules

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.