tech-debt-analyzer

Identify, categorize, and prioritize technical debt in JavaScript and TypeScript codebases.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Mohamed-Elkahef/test-project --skill tech-debt-analyzer-mohamed-elkahef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-analyzer
Source: https://github.com/Mohamed-Elkahef/test-project/tree/main/.claude/skills/tech-debt-analyzer
Command: npx skills add https://github.com/Mohamed-Elkahef/test-project --skill tech-debt-analyzer-mohamed-elkahef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Unmanaged technical debt slows development velocity, increases bug rates, and raises maintenance costs by making codebases harder to modify and extend. This skill provides a structured, repeatable process to surface, assess, and address debt before it impacts delivery.

Core Features & Use Cases

  • Automated Code Analysis: Run scripts to detect code smells, complex functions, large files, and weak typing across JavaScript/TypeScript codebases.
  • Dependency Health Checks: Identify deprecated packages, duplicate functionality, and unsafe version constraints in project dependencies.
  • Standardized Documentation: Use pre-built templates for technical debt registers and architecture decision records (ADRs) to track debt and document major technical choices.
  • Use Case: A development team preparing for a major feature launch can use this skill to run a full debt audit, prioritize high-impact issues, and allocate sprint capacity to debt remediation to avoid blocking new work.

Quick Start

Use the tech-debt-analyzer skill to run a full technical debt audit of your codebase and generate a prioritized list of debt items with remediation plans.

Frequently Asked Questions about tech-debt-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify and categorize technical debt in a JavaScript codebase?

To identify technical debt in a JavaScript codebase, you can run automated code analysis scripts that detect code smells, complex functions, large files, and weak typing. This process categorizes debt items to reduce maintenance overhead and improve long-term code maintainability.

Can I audit deprecated packages and unsafe version constraints in my project dependencies?

Yes, you can perform dependency health checks to identify deprecated packages, duplicate functionality, and unsafe version constraints in project dependencies. This dependency issue analysis helps surface potential risks before they impact your development delivery.

What is the best way to prioritize technical debt remediation for sprint planning?

The best way to prioritize technical debt remediation is to run a full debt audit that generates a prioritized list of debt items with actionable remediation plans. This allows teams to allocate sprint capacity to high-impact issues before a major feature launch.

Does this technical debt analysis work with TypeScript codebases?

Yes, this technical debt analysis works with both JavaScript and TypeScript codebases. It detects weak typing, complex functions, and large files across your project to provide a structured, repeatable process for assessing debt.

How do I document technical debt and major architectural decisions?

You can document technical debt and major architectural decisions using pre-built templates for technical debt registers and architecture decision records (ADRs). This standardized documentation tracks debt systematically and records major technical choices.