tech-debt

Prioritize technical debt by scanning for TODOs, FIXMEs, duplication, and missing tests, then ranking findings from P0 to P3 based on production risk and delivery blockage. This approach outputs a prioritized remediation table with file locations and recommended attack order.

Identify deprecated dependencies and hardcoded configuration by scanning the codebase for known anti-patterns and categorizing them by operational cost. The process flags these issues with specific file and line locations to calculate improvement value.

Risk-based classification for codebase maintenance evaluates findings on production risk, delivery blockage, operational cost, and improvement value. It assigns each technical debt item a priority from P0 to P3 to guide stabilization work before feature development.

Yes, technical debt scanning locates deprecated dependencies and missing tests in critical code to prepare for upgrades. It generates a prioritized table of findings with estimated effort to sequence dependency updates safely.

Technical debt scanning does locate missing tests within critical code areas by searching for gaps alongside TODOs and duplication. It includes these gaps in the prioritized P0 to P3 findings to highlight delivery blockage risks.

Scanning a module for technical debt is limited to locating static patterns like TODOs, FIXMEs, duplication, and hardcoded configuration. It produces prioritized findings but does not automatically refactor the code or resolve the operational risks it identifies.