technical-debt-analyzer

Analyze codebases to detect, categorize, and prioritize technical debt.

142|14|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill technical-debt-analyzer-arabelatso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-debt-analyzer
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/technical-debt-analyzer
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill technical-debt-analyzer-arabelatso

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify, categorize, and prioritize technical debt within a codebase, leading to improved code quality, reduced maintenance costs, and a healthier software project.

Core Features & Use Cases

  • Code Smells & Complexity: Detects issues like long methods, duplicated code, and high cyclomatic complexity.
  • Architectural Issues: Identifies tight coupling, missing abstractions, and layer violations.
  • Maintenance Risk: Pinpoints areas with high change frequency, bug density, or outdated dependencies.
  • Test & Documentation Debt: Assesses gaps in test coverage and missing documentation.
  • Use Case: Before a major refactoring effort, use this Skill to get a comprehensive report on the most critical areas of technical debt, allowing you to focus your efforts effectively.

Quick Start

Analyze the current codebase for technical debt and provide a prioritized list of issues.

Frequently Asked Questions about technical-debt-analyzer

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

FAQPage Schema
How do I identify technical debt in a codebase before refactoring?

Code analysis detects technical debt by evaluating code complexity, duplicated code, and architectural issues like tight coupling. It categorizes these issues and prioritizes fixes based on their maintenance risk and impact, offering actionable recommendations for your refactoring effort.

What is the best way to prioritize code quality issues for maintenance?

Prioritize code quality issues by analyzing the codebase for maintenance risks, test coverage gaps, and architectural issues. This evaluates the impact and effort of each problem, categorizing technical debt to provide a prioritized list of actionable recommendations for maintenance.

Can I detect architectural issues and tight coupling with a code analysis tool?

Yes, you can detect architectural issues such as tight coupling, missing abstractions, and layer violations using code analysis. This identifies architectural technical debt within the codebase, providing actionable recommendations to improve software engineering structure and reduce maintenance risks.

How do I assess test coverage gaps and missing documentation as technical debt?

Assess test and documentation debt by analyzing the codebase for missing documentation and insufficient test coverage. This identifies technical debt related to maintenance risks, providing actionable recommendations to improve code quality and reduce software engineering maintenance costs.

Does code analysis work for finding outdated dependencies and maintenance risks?

Yes, code analysis works for finding maintenance risks by pinpointing areas with high change frequency, bug density, and outdated dependencies. This detects technical debt within the codebase, providing prioritized recommendations based on impact and effort to lower maintenance costs.