analyze-tech-debt

Technical debt identification scans your TypeScript/TSX source files to detect security vulnerabilities like hardcoded secrets, performance issues such as N+1 queries and infinite re-renders, code complexity, duplication, and test coverage gaps. The process produces a markdown report categorized by severity with per-file details and prioritized remediation actions.

The analysis detects five core issue categories: security vulnerabilities (hardcoded secrets), performance problems (N+1 queries, infinite re-renders), code complexity violations, duplicate code patterns, and test coverage gaps. Each finding includes file location, line number, impact assessment, and recommended priority for fixing.

Yes, the analysis applies across your entire src directory for TypeScript and TSX files. It scans all sources in scope, aggregates findings by severity and category, and generates a unified prioritized report with actionable recommendations for systematic remediation.

The analysis produces severity-based categories and a summarized priority ranking with recommended actions. Security vulnerabilities and performance issues typically receive highest priority, followed by code complexity and coverage gaps, allowing you to plan fixes systematically rather than arbitrarily.

The analysis generates a markdown-formatted report organized by severity levels, with per-file details listing the file path, line number, specific issue, and impact. This structure enables easy review, sharing, and integration into your refactoring workflow and documentation.