debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/li3p/skills --skill debt-scan-li3p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debt-scan
Source: https://github.com/li3p/skills/tree/main/skills/debt-scan
Command: npx skills add https://github.com/li3p/skills --skill debt-scan-li3p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debt-scan helps teams identify and prioritize technical debt across a repository to turn code smells into actionable cleanup work.

Core Features & Use Cases

  • Identify hotspots of debt in code and architecture.
  • Prioritize remediation based on impact, effort, and risk.
  • Generate actionable tickets and roadmaps for engineering teams.

Quick Start

Run a debt-scan on the repository to generate a prioritized remediation plan.

Frequently Asked Questions about debt-scan

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

FAQPage Schema
How do I identify technical debt hotspots in my codebase?

To identify technical debt hotspots in your codebase, you can run an automated static analysis to evaluate code quality signals and risk factors. This process surfaces actionable debt items to guide your remediation planning.

What is the best way to prioritize technical debt for backlog grooming?

The best way to prioritize technical debt for backlog grooming is to assess code health based on impact, effort, and risk. This approach generates a prioritized remediation roadmap for engineering teams.

Can I generate actionable remediation tickets from static analysis results?

Yes, you can generate actionable remediation tickets from static analysis results by evaluating code quality signals and risk factors. This turns identified code smells into structured cleanup work for your team.

When do I need a technical debt assessment for release readiness?

You need a technical debt assessment for release readiness when you must surface actionable debt items that pose risk factors. Applying this scan during code health assessments ensures your repository meets quality standards.

Does technical debt analysis work without specific code quality tools or dependencies?

Technical debt analysis requires automated analysis of code quality signals and risk factors within your repository. The scan operates independently to generate a prioritized remediation plan without requiring external components.