tech-debt

Name: tech-debt
Availability: InStock
Author: bswrundquist

Scan codebases for debt markers, complexity, dead code, and code smells.

Updated Mar 9, 2026

Search Tags:#code quality #code analysis #refactoring #maintainability #tech debt #developer tooling

Ready to run

npx skills add https://github.com/bswrundquist/devtools --skill tech-debt-bswrundquist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/tech-debt
Command: npx skills add https://github.com/bswrundquist/devtools --skill tech-debt-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers proactively identify, categorize, and prioritize technical debt within a codebase, leading to improved code health and maintainability.

Core Features & Use Cases

Scan for explicit debt markers (TODO, FIXME, HACK, XXX).
Analyze code complexity (large files, complex functions).
Detect dead code (unused imports, functions).
Check type coverage (missing type hints).
Identify code smells and anti-patterns.
Prioritize findings by impact and effort.
Use Case: A development team can use this Skill at the end of a sprint to generate a report of all technical debt, allowing them to allocate resources for refactoring in the next sprint.

Quick Start

Run the tech-debt skill to scan the current project for all explicit debt markers and complex functions.

Frequently Asked Questions about tech-debt

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

FAQPage Schema

How do I identify technical debt in a codebase?▼

To identify technical debt, scan for explicit markers like TODO and FIXME, analyze code complexity, detect dead code, check type coverage, and identify code smells to produce a prioritized refactoring report.

What's the best way to catalog technical debt for a sprint review?▼

Catalog technical debt by scanning the project for explicit markers, analyzing complex functions, and prioritizing findings by impact and effort to generate a resource allocation report for the next sprint.

Can I prioritize refactoring efforts based on code complexity and dead code?▼

Yes, you can prioritize refactoring efforts by analyzing large files, complex functions, and unused imports to generate a prioritized report that guides developer resources toward high-impact debt.

Does technical debt scanning detect missing type hints and code smells?▼

Yes, technical debt scanning detects missing type hints and identifies code smells or anti-patterns, alongside scanning for FIXME and HACK markers to improve overall code maintainability.

When do I need to analyze dead code and type coverage for maintainability?▼

Analyze dead code and type coverage when proactively managing code health, allowing your development team to identify unused functions and missing type hints before they compound into maintainability issues.