tech-debt

To scan your codebase for tech debt, this skill analyzes your repository to surface TODOs, FIXMEs, and deprecated patterns, outputting a prioritized markdown task list. Findings are ranked by impact, effort, and risk to guide your remediation.

Tracking outdated patterns and missing tests across large modules requires automated discovery. This skill scans files across your specified scope to identify maintenance gaps and produces a markdown task list with risk weighting to guide targeted fixes.

Yes, you can apply tech debt detection within a user-specified scope instead of the entire repository. This allows you to focus the automated discovery on critical modules to efficiently generate a targeted, actionable backlog.

Yes, the tech debt report includes risk weighting for findings like deprecated APIs. It ranks all discovered maintenance gaps and outdated patterns by impact, effort, and risk to produce a prioritized markdown task list for remediation.

Automated tech debt discovery requires scanning project documentation, specifically your AGENTS.md file. It also checks for preference to test coverage to accurately identify maintenance gaps and generate the prioritized markdown task list.

You should run a tech debt scan when maintaining a large Rust or OSS codebase to produce an actionable backlog of tech-debt tasks. It is ideal for surfacing accumulated TODOs and deprecated patterns before they impact project stability.