tech-debt-analyzer

Technical debt analysis identifies issues across code, architecture, testing, dependencies, documentation, and infrastructure. It calculates quality metrics including complexity, duplication, and test coverage to help prioritize remediation efforts.

Technical debt prioritization scores debt items based on their impact and remediation effort. This framework helps allocate development capacity strategically during sprint planning by highlighting critical areas like low test coverage in security-sensitive modules.

Identifying refactoring targets involves measuring code quality metrics such as complexity and duplication. This Skill detects technical debt across multiple categories and provides a scoring framework to pinpoint the most critical areas for codebase improvement.

Yes, you can use technical debt analysis during sprint planning to assess current debt levels. It helps identify critical areas, such as low test coverage in security-sensitive modules, allowing you to allocate development capacity for targeted remediation.

This analyzer detects technical debt across six categories: code, architecture, testing, dependencies, documentation, and infrastructure. It quantifies these issues to support strategic decision-making for refactoring and debt reduction initiatives.

Yes, technical debt analysis works without external dependencies. The Skill operates independently to analyze source code and calculate quality metrics, providing prioritization frameworks for debt reduction directly from the current project.