skills.rest
tgsatwit
tgsatwitCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt-score

Quantifies technical debt types and estimates carrying costs and remediation efforts for software codebases.

Updated Aug 23, 2026
Search Tags:#code quality#software engineering#refactoring#maintenance#technical debt#prioritization
One-click install
npx skills add https://github.com/tgsatwit/agent-delivery-pub --skill tech-debt-score
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-score
Source: https://github.com/tgsatwit/agent-delivery-pub/tree/main/.claude/skills/tech-debt-score
Command: npx skills add https://github.com/tgsatwit/agent-delivery-pub --skill tech-debt-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill makes technical debt visible and measurable, transforming vague refactoring discussions into evidence-based maintenance investment decisions.

Core Features & Use Cases

  • Debt Classification: Assesses debt by type (design, code, test, dependency, documentation, infrastructure).
  • Carrying Cost Assessment: Estimates the ongoing cost of not fixing debt using velocity drag and risk exposure.
  • Remediation Prioritization: Calculates a priority score based on carrying cost and estimated remediation effort.
  • Use Case: Before allocating maintenance budget, use this Skill to identify and prioritize the most impactful technical debt items, ensuring that critical issues are addressed first.

Quick Start

Assess the technical debt for the 'user-authentication-module'.

Frequently Asked Questions about tech-debt-score

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

FAQPage Schema
How do I quantify technical debt across a software module?▼

You can quantify technical debt by classifying debt types and estimating carrying costs versus remediation efforts. This Skill evaluates modules to generate a prioritized debt register, transforming vague refactoring needs into measurable maintenance investment data.

What is the best way to prioritize refactoring tasks in a codebase?▼

Prioritizing refactoring is best done by calculating a priority score based on carrying cost and remediation effort. This approach identifies the most impactful technical debt items, ensuring critical maintenance issues are addressed before others.

What types of technical debt can be assessed for maintenance allocation?▼

Technical debt types assessed include design, code, test, dependency, documentation, and infrastructure debt. Classifying these categories allows you to accurately estimate ongoing carrying costs and plan targeted maintenance allocation.

How do I estimate the carrying cost of not fixing technical debt?▼

Estimate the carrying cost of technical debt by evaluating velocity drag and risk exposure. This calculation reveals the ongoing cost of not fixing debt, providing an evidence-based metric for maintenance investment decisions.

Do I need architecture standards and tech radar context to assess technical debt?▼

Yes, comprehensive technical debt analysis requires context from architecture standards, build standards, tech radar, velocity cells, and risk registers. This contextual data ensures accurate debt classification and reliable remediation prioritization.

Related Skills

Explore More Software Engineering Skills→
jerelvelardejerelvelarde
6

manage-tech-debt

Track and prioritize technical debt in a codebase register.

Community
Advanced
cslsoftwarescslsoftwares

quality-tech-debt-tracker

Register, classify, and prioritize technical debt with maintenance costs and remediation paths.

Community
Advanced
bswrundquistbswrundquist

tech-debt

Scan codebases for debt markers, complexity, dead code, and code smells.

Community
Intermediate
JylhisJylhis
1

golang-security

Detect Go vulnerabilities using govulncheck, static analysis, and DREAD scoring.

Community
Advanced