li3p/debt-scan

Debt Scan

Produce a prioritized technical debt report for the current repository.

Scan Dimensions

Check the repository for:

• large files or modules with too many responsibilities
• long functions and deeply nested control flow
• high import count or strong coupling
• dependency staleness and deprecations
• source files without nearby tests
• risky suppressions such as eslint-disable, ts-ignore, or type: ignore
• broad any usage or unsafe casts
• TODO/FIXME/HACK comments, especially old ones
• duplicated logic
• direct database access outside the expected layer
• business logic inside route handlers or controllers
• circular dependencies when tooling is available
• memory growth risks, unbounded queues, and global mutable state

Prioritization

Group findings by:

• High: likely to cause incidents, data loss, security issues, or block feature work.
• Medium: increases maintenance cost or regression risk.
• Low: local quality improvement with limited blast radius.

For each finding include:

• location
• issue
• likely impact
• estimated effort: small, medium, or large
• ticket-style title

End with a recommended fix order based on impact-to-effort ratio. Do not modify files unless the user asks.