techdebt

Scan multi-language repositories for duplicated code, dead exports, unused dependencies, stale TODOs, and bloated files.

4|Updated Jan 31, 2026

Search Tags:#code quality #tech debt #TODOs #duplicates #dead exports #bloated files

Ready to run

npx skills add https://github.com/ramonclaudio/skills --skill techdebt-ramonclaudio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/ramonclaudio/skills/tree/main/plugins/techdebt/skills/techdebt
Command: npx skills add https://github.com/ramonclaudio/skills --skill techdebt-ramonclaudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast, end-of-session sweep to surface lightweight code debt. It helps teams quickly identify duplicated blocks, dead exports, unused dependencies, stale TODOs, and oversized files, so you can tidy up before shipping.

Core Features & Use Cases

Dedupe & dead code detection: finds duplicated code blocks across the repo and flags the locations.
Unused exports & dead imports: detects public exports that are never imported anywhere (excluding entrypoints).
TODO hygiene & file bloat: surfaces stale TODOs without linked issues and files larger than typical thresholds.
Scoped quick fixes: groups findings by severity and suggests fast, mechanical fixes that can be applied in seconds.
Use Case: run a rapid health check at the end of a development sprint to ship leaner, safer code.

Quick Start

Run the techdebt skill at the repository root to start a fast scan. Use --dry-run to preview findings, or pass a path to scope the analysis.

Frequently Asked Questions about techdebt

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

FAQPage Schema

How do I scan a codebase for tech debt, duplicates, and stale TODOs?▼

To scan a codebase for tech debt, run a sweep at the repository root to identify duplicates, dead exports, unused dependencies, stale TODOs, and bloated files across multi-language repositories. It returns a structured, fix-oriented report for quick actions.

What is the best way to detect dead exports and unused dependencies before shipping?▼

The best way to detect dead exports and unused dependencies is an end-of-session sweep that flags public exports never imported anywhere, excluding entrypoints, alongside unused dependencies. It groups findings by severity for fast, mechanical fixes.

Can I run a quick health check for file bloat and duplicated code blocks in a multi-language repository?▼

Yes, you can run a quick health check for file bloat and duplicated code in a multi-language repository. The scan applies across multiple languages, surfaces oversized files and duplicated blocks, and suggests fast, scoped quick fixes.

How do I preview tech debt findings without modifying my code?▼

To preview tech debt findings without modifying code, run the scan in a dry-run mode at the repository root. This surfaces the report of hotspots, including dead code and stale TODOs, so you can review them before applying any changes.

Does a lightweight tech debt sweep work across different programming languages in one scan?▼

Yes, a lightweight tech debt sweep works across different programming languages in one scan. It is designed to apply across multi-language repositories to identify duplicates, dead exports, and bloated files simultaneously.