tech-debt

Scan codebases for debt indicators and generate prioritized sprint recommendations.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill tech-debt-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/tech-debt
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill tech-debt-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unmanaged technical debt accumulates over time, slowing development velocity, increasing bug risk, and making codebases harder to maintain. This skill eliminates ad-hoc, untracked tech debt by providing a structured system to identify, log, and address debt items systematically.

Core Features & Use Cases

  • Automated Debt Scanning: Detect common tech debt indicators across the codebase, including TODO/FIXME comments, deprecated code markers, duplicated logic blocks, and oversized files or functions.
  • Centralized Debt Register: Maintain a single, version-controlled record of all tech debt items, with assigned categories, impact assessments, and estimated fix efforts.
  • Prioritization & Reporting: Score debt items by impact and fix effort to generate sprint-ready prioritization lists, plus trend reports to track debt growth or reduction over time. Use Case: For a team with a legacy codebase full of unlogged workarounds and outdated patterns, use this skill to run a full scan, log all findings to a shared register, and get a prioritized list of high-impact items to tackle in the next sprint.

Quick Start

Use the tech-debt skill to run a full scan of your codebase for technical debt indicators and save the findings to the project's debt register.

Frequently Asked Questions about tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track and categorize technical debt across my codebase?

Scan your codebase to track technical debt by detecting TODO/FIXME comments, deprecated code, duplicated logic, and oversized files, then log findings into a centralized debt register with impact and effort estimates.

What is a centralized debt register and how does it help manage code maintenance?

A centralized debt register is a version-controlled record of all technical debt items, assigned categories, impact assessments, and estimated fix efforts. This structured system eliminates ad-hoc, untracked debt to reduce maintenance overhead and prevent unplanned work.

How do I prioritize technical debt items for sprint planning?

Prioritize technical debt items for sprint planning by scoring them based on impact and fix effort to generate sprint-ready prioritization lists, ensuring teams systematically repay debt without disrupting feature delivery.

Can I generate trend reports to monitor technical debt reduction over time?

Yes, you can generate trend reports to monitor technical debt growth or reduction over time, helping development teams systematically address unlogged workarounds and outdated patterns while tracking maintenance progress.

What is the best way to scan for TODO/FIXME comments and deprecated code?

The best way to scan for TODO/FIXME comments and deprecated code is using automated debt scanning, which detects these common indicators across your codebase alongside duplicated logic blocks and oversized files or functions.

Does technical debt scanning work for legacy codebases with unlogged workarounds?

Yes, technical debt scanning works for legacy codebases with unlogged workarounds by running a full scan, logging all findings to a shared register, and generating a prioritized list of high-impact items to tackle in the next sprint.