skills.rest
meleantonio
meleantonioCOMMUNITY
Explore all skills by this author →
Website𝕏@antoniomele101GitHub

techdebt

Scan codebases for technical debt and apply deterministic fixes.

598|128|Updated Jan 26, 2026
Search Tags:#refactoring#maintainability#code-quality#static-analysis#lint#code-cleanup#technical-debt
One-click install
npx skills add https://github.com/meleantonio/awesome-econ-ai-stuff --skill techdebt-meleantonio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/meleantonio/awesome-econ-ai-stuff/tree/main/_skills/engineering/techdebt
Command: npx skills add https://github.com/meleantonio/awesome-econ-ai-stuff --skill techdebt-meleantonio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and fix technical debt in a codebase, including duplicated code, dead code, outdated patterns, and code smells, to improve maintainability.

Core Features & Use Cases

  • Scan the repository for duplication, dead code, deprecated patterns, and common code smells.
  • Report issues with file paths, severity, and suggested fixes, then guide deterministic refactoring steps.
  • Verify improvements by running linters and tests to ensure stability before release.

Quick Start

Run the techdebt command to scan the codebase, report findings, and apply high-impact cleanups.

Frequently Asked Questions about techdebt

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

FAQPage Schema
How do I find and fix technical debt in my codebase?▼

To find technical debt, you scan a codebase to identify duplicated code, dead code, outdated patterns, and code smells. The process reports issues with file paths, severity, and suggested fixes to guide deterministic refactoring steps.

What is the best way to automate code cleanup and refactoring before a release?▼

The best way to automate code cleanup is using a deterministic workflow of scan, report, fix, and verify. This approach applies high-impact refactoring and runs local linters and tests to ensure stability before release.

How does static analysis detect code smells and dead code for maintainability?▼

Static analysis detects code smells and dead code by scanning the repository for deprecated patterns and structural duplication. It then generates a report detailing file paths and severity to improve overall maintainability.

Can I run linters and tests to verify refactoring stability during end-of-session cleanup?▼

Yes, you can run local linters and tests to verify refactoring stability during end-of-session cleanup. This ensures applied cleanups and code refactoring do not break existing functionality before release.

Do I need any dependencies or specific scripts to scan for code smells and technical debt?▼

No specific dependencies are required to scan for technical debt, though the workflow supports optional scripts, references, and assets directories. It relies on local linters and tests to verify improvements.

Related Skills

Explore More Software Engineering Skills→
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
marcospmailmarcospmail

run-e2e-tests

Automate end-to-end test suites for the Yato tmux orchestrator.

Community
Intermediate
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
Next-ofkinNext-ofkin
1

code-review-ai-ai-review

Automate code review with static analysis and AI models.

Community
Advanced