Scan codebases for technical debt markers and prioritize a markdown debt register.
npx skills add https://github.com/emcconnell/nova-scout --skill tech-debt-emcconnell
Please help me install this Agent Skill. Skill: tech-debt Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/tech-debt Command: npx skills add https://github.com/emcconnell/nova-scout --skill tech-debt-emcconnell
Untracked technical debt accumulates as TODOs, hacks, large/complex files, duplicated code, deprecated APIs, and missing tests, making maintenance slow and risky. This Skill centralizes discovery, categorization, and tracking so teams can make conscious trade-offs and plan remediation work.
Run the tech-debt skill with the scan subcommand to detect debt indicators and optionally append findings to docs/tech-debt-register.md.
High-intent search queries and answers about installing and using this skill.
You can scan a codebase for technical debt by locating TODO, FIXME, and HACK markers, @deprecated tags, large files over 500 lines, long functions over 50 lines, and duplicated code patterns. The scan results can then be appended to a markdown debt register.
Technical debt prioritization is computed by scoring items based on impact multiplied by encounter frequency, then divided by estimated effort. This formula allows teams to re-sort the debt register and identify top items for the next sprint backlog.
Yes, manual technical debt items can be appended with custom impact and effort metadata. These entries are maintained alongside automated scan findings in a central markdown register located at docs/tech-debt-register.md.
Yes, tracking technical debt includes scanning for @deprecated tags and detecting duplicated code patterns. It also identifies large files, long functions, and standard markers like TODO and HACK to centralize discovery.
Technical debt reporting generates read-only trend and category summary reports from the maintained markdown register. These reports summarize discovered debt categories to help teams make conscious trade-offs and plan remediation work.
The technical debt register is limited to a single markdown file at docs/tech-debt-register.md. It supports append, read, and write flows for debt entries but provides read-only reporting without integration into external issue tracking systems.
nikhillinitDetect and prioritize technical debt with configurable thresholds and SQALE metrics.
nuoyanruoshuiScan codebases for debt indicators and manage prioritized debt registers.
HomericIntelligenceDetect code smells and complexity issues in codebases.
troykellyDetect TODO, FIXME, and HACK patterns and enforce immediate action or tracked deferral.
