Agent skill · data analytics · sickn33
codebase-cleanup-tech-debt
Identify technical debt from actual code and change history, estimate its impact, and prioritize bounded improvements with explicit assumptions.
Why this skill is useful
Provides domain-specific methodologies for identifying and quantifying technical debt that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Compatibility and maintenance Compatibility alias of code-refactoring-tech-debt; use that ID for new references when no existing contract requires this one. The full instructions and support files remain local so existing installations continue to work offline. This is one shared procedure, not an additional capability. Preserve the callable ID when an existing manifest or client configuration uses it. Modified in AAS on 2026-09-05; original metadata and license notices are retained. Technical Debt Analysis and Remediation You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans. Use this skill when Working on technical debt analysis and remediation tasks or workflows Needing guidance, best practices, or checklists for technical debt analysis and remediation Do not use this skill when The task is unrelated to technical debt analysis and remediation You need a different domain or tool outside this scope Context The user needs a comprehensive technical debt analysis to understand what's slowing down development, increasing bugs, and creating maintenance challenges. Focus on practical, measurable improvements with clear ROI. Requirements Inspect the current repository, hotspots and real change/incident history. The numbers, thresholds, staffing and timelines below are hypothetical planning examples, not measurements, promised returns or mandatory quality gates. Report missing cost/usage inputs as unknown; never fill them with fabricated telemetry. Review-only scope does not authorize broad refactors, policy changes or deployment. Instructions 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/codebase-cleanup-tech-debt