Agent skill · data analytics · aj-geddes
technical-debt-assessment
Assess, quantify, and prioritize technical debt using code analysis, metrics, and impact analysis. Use when planning refactoring, evaluating codebases, or making architectural decisions.
Why this skill is useful
Provides domain-specific knowledge and metrics for assessing technical debt that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Technical Debt Assessment Table of Contents Overview When to Use Quick Start Reference Guides Best Practices Overview Systematically identify, measure, and manage technical debt to make informed decisions about code quality investments. When to Use Legacy code evaluation Refactoring prioritization Sprint planning Code quality initiatives Acquisition due diligence Architectural decisions Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Technical Debt Calculator Technical Debt Calculator Code Quality Scanner Code Quality Scanner Best Practices ✅ DO Quantify debt impact Prioritize by ROI Track debt over time Include debt in sprints Document debt decisions Set quality gates ❌ DON'T Ignore technical debt Fix everything at once Skip impact analysis Make emotional decisions
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/technical-debt-assessment