Tech Debt Analyzer

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

473 stars 117 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ailabs-393/ai-labs-claude-skills --skill tech-debt-analyzer
Manual install
git clone --depth 1 https://github.com/ailabs-393/ai-labs-claude-skills.git /tmp/ai-labs-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-labs-claude-skills/packages/skills/tech-debt-analyzer ~/.claude/skills/tech-debt-analyzer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Technical Debt Analyzer

## Overview

Systematically identify, analyze, document, and track technical debt in JavaScript/TypeScript codebases. This skill provides automated analysis tools, comprehensive debt categorization frameworks, and documentation templates to maintain a technical debt register.

## Core Workflow

### 1. Automated Analysis

Run automated scripts to detect technical debt indicators across the codebase.

#### Code Smell Detection

Identify code quality issues using the automated detector:

```bash
python3 scripts/detect_code_smells.py src --output markdown
```

The script analyzes:
- **Large Files:** Files exceeding 500 lines
- **Complex Functions:** High cyclomatic complexity (>10) or long functions (>50 lines)
- **Debt Markers:** TODO, FIXME, HACK, XXX, BUG comments
- **Console Statements:** Debug statements left in code
- **Weak Typing:** Use of `any` type in TypeScript
- **Long Parameters:** Functions with >5 parameters
- **Deep Nesting:** Code nested >4 levels deep
- **Magic Numbers:** Hardcoded numeric values

**Output Example:**
```
# Technical Debt Analysis Report

**Files Analyzed:** 127
**Total Lines:** 15,432
**Total Issues:** 89

### Issues by Severity
- HIGH: 23
- MEDIUM: 41
- LOW: 25

## Large Files (12 issues)
### High Priority
- src/components/Dashboard.tsx (847 lines): File too large
- src/services/DataProcessor.ts (623 lines): File too large
...
```

#### Dependency Analysis

Examine dependencies for debt indicators:
Read the full skill on GitHub

Details

Skill name
tech-debt-analyzer
Path
packages/skills/tech-debt-analyzer/SKILL.md
License
MIT
Repo updated
11 November 2025

FAQ

What does the Tech Debt Analyzer skill do?

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

How do I install the Tech Debt Analyzer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ailabs-393/ai-labs-claude-skills --skill tech-debt-analyzer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tech Debt Analyzer popular?

It lives in ailabs-393/ai-labs-claude-skills, which has 473 GitHub stars and 117 forks.

Related skills

Brand Analyzer

473

ailabs-393/ai-labs-claude-skills

This skill should be used when the user requests brand analysis, brand guidelines creation, brand audits, or establishing brand identity and consistency standards. It provides comprehensive frameworks for analyzing brand elements and creating actionable brand guidelines based on requirements.

Frontend & Design117

Business Analytics Reporter

473

ailabs-393/ai-labs-claude-skills

This skill should be used when analyzing business sales and revenue data from CSV files to identify weak areas, generate statistical insights, and provide strategic improvement recommendations. Use when the user requests a business performance report, asks to analyze sales data, wants to identify areas of weakness, or needs recommendations on business improvement strategies.

Marketing, Sales & Business117

Business Document Generator

473

ailabs-393/ai-labs-claude-skills

This skill should be used when the user requests to create professional business documents (proposals, business plans, or budgets) from templates. It provides PDF templates and a Python script for generating filled documents from user data.

Marketing, Sales & Business117

Domain Discovery

360

TanStack/intent

Use when the maintainer explicitly requests full-library discovery or a skill taxonomy review. For an agreed skill batch or a concrete code/docs update, use generate-skill instead.

Software Development26

Rocprofiler Systems Instrumenting Binaries

500

amd/skills

Guides instrumentation with `rocprof-sys-instrument` - choosing runtime instrumentation vs binary rewrite (`-o`), including or excluding functions and modules with regex options, previewing what will be instrumented with a dry run (`--simulate`, `--dump-info`, `--print-*`), tuning granularity (`--min-instructions`, `--min-address-range`, `--instrument-loops`), rewriting libraries, and diagnosing why a function is missing from, or too numerous in, a trace. Use when the user asks about rocprof-sys-instrument, binary rewrite, instrumenting a shared library, function or module include/exclude rege

Software Development47

Generate Skill

360

TanStack/intent

Use when creating or extending library skill batches, updating guidance after library source or docs change, configuring repository skill distribution, or acting on an Intent review report, including when the maintainer asks only for the library change. For full-library discovery or taxonomy design, use domain-discovery; for generating an approved full-library tree, use tree-generator.

Software Development26

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.