skills.rest
foutoucour
foutoucourCOMMUNITY
Explore all skills by this author →
𝕏@jordiriera_cgGitHub

technical-debt-radar

Identify and quantify technical debt with remediation effort estimates and risk scores.

Updated Mar 24, 2026
Search Tags:#architecture#prioritization#code-quality#risk-assessment#code-smells#technical-debt
One-click install
npx skills add https://github.com/foutoucour/guitar-match --skill technical-debt-radar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt-radar
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/technical-debt-radar
Command: npx skills add https://github.com/foutoucour/guitar-match --skill technical-debt-radar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill identifies and quantifies technical debt in codebases, turning vague cleanup ideas into measurable, actionable items with ownership and priority.

Core Features & Use Cases

  • Surface code smells, dependency health issues, architecture erosion, test debt, and documentation debt across the project.
  • Generate remediation effort estimates (hours), blast radius (number of affected files), and risk scores to help planning.
  • Provide a structured debt inventory that can be shared with product and tech leads to negotiate scope and timelines.

Quick Start

Scan the target directory to surface, quantify, and prioritize actionable technical debt items.

Frequently Asked Questions about technical-debt-radar

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

FAQPage Schema
How do I measure technical debt to prioritize code cleanup tasks?▼

You can measure technical debt by scanning a codebase to surface code smells, dependency health, architecture erosion, test debt, and documentation debt. This process generates remediation effort estimates, blast radius, and risk scores for prioritization.

What is the best way to estimate remediation effort hours for code smells?▼

The best way to estimate effort hours is to run a debt analysis that calculates remediation effort alongside blast radius and risk scores. This quantifies code smells and dependency issues into actionable hourly estimates for planning.

Can I assess technical debt across different programming languages and project sizes?▼

Yes, technical debt assessment works across languages and project sizes. It surfaces architecture erosion, test debt, and documentation debt in real projects regardless of scale, producing a structured debt inventory for stakeholders.

How do I generate a technical debt inventory for product and tech leads?▼

Generate a technical debt inventory by scanning the target directory to identify and quantify debt items. The output is a structured inventory that includes risk scores and effort estimates, making debt negotiable with stakeholders.

Does this technical debt analysis require any specific dependencies or components?▼

No specific dependencies or components are required to perform the analysis. You scan the target directory directly to surface code smells, dependency health issues, and architecture erosion without external tool prerequisites.

Related Skills

Explore More Software Engineering Skills→
krrishverma1805-webkrrishverma1805-web

GSD Codebase Mapper

Analyze codebase structure, dependencies, patterns, and technical debt using PowerShell.

Community
Advanced
hohai99hohai99

long-term-debt-tracker

Tracks, categorizes and prioritizes technical debt into actionable backlog items.

Community
Basic
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate
686f6c61686f6c61
105

sonarqube

Automate SonarQube code quality analysis with Docker and quality gates.

Community
Advanced