skills.rest
ArthTech-AI
ArthTech-AIOFFICIAL
Explore all skills by this author →
GitHub

tech-debt

Detect technical debt across codebases with file-cited severity findings.

Updated Aug 27, 2026
Search Tags:#technical debt#code audit#code smells#duplication#dead code#deprecated patterns#baseline tracking
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill tech-debt-arthtech-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/tech-debt
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill tech-debt-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies accumulated technical debt that slows teams down, including duplication, dead code, design smells, coupling issues, and outdated patterns. It helps you turn a sprawling codebase into a prioritized, file-cited cleanup plan instead of a vague refactor wish list.

Core Features & Use Cases

  • Holistic debt auditing: Scans a repository or a focused scope for DRY violations, dead code, code smells, design drift, and deprecated practices.
  • Severity-ranked reporting: Produces critical, important, and suggestion-level findings with exact file and line citations.
  • Baseline tracking: Saves a reusable baseline so future audits can detect new, resolved, and already-tracked findings over time.
  • Use case: Run it after an AI-heavy implementation cycle to quickly spot duplication, orphaned code, and architecture decay before the next release.

Quick Start

Ask the tech-debt skill to audit your repository for duplication, dead code, and outdated patterns, then generate a severity-ranked report with file citations.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I audit my codebase for technical debt and code smells?▼

To audit your codebase for technical debt, scan the repository for duplication, dead code, code smells, coupling issues, and deprecated patterns. The audit generates a severity-ranked report with exact file and line citations to guide your cleanup.

What is the best way to track new technical debt against a previous baseline?▼

Tracking new technical debt against a previous baseline requires saving a reusable audit snapshot. Future delta tracking compares new scans against this baseline to identify newly introduced, resolved, and already-tracked findings over time.

Can I detect dead code and DRY violations in a specific scope instead of the whole repository?▼

Yes, you can detect dead code and DRY violations in a specific scope. The audit supports both whole-repository and scoped analysis, allowing you to target focused areas for duplication and orphaned code detection.

How do I deduplicate technical debt findings against existing QA incidents?▼

To deduplicate technical debt findings against existing QA incidents, the audit cross-references new findings with tracked issues. This deduplication prevents redundant reporting and ensures reliable trend tracking across your codebase.

Why prioritize technical debt findings by severity tiers?▼

Prioritizing technical debt findings by severity tiers transforms a sprawling codebase into a focused cleanup plan. Critical, important, and suggestion-level rankings help teams address architecture decay before the next release.

Related Skills

Explore More Software Engineering Skills→
az9713az9713

dark-code-suite-init

Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.

Community
Intermediate
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
constellizeconstellize
1

assess-operational-knowledge-health

Assess operational knowledge decay and produce a prioritized action plan.

Official
Advanced
Vivekmano27Vivekmano27

static-analysis

Run tool-based static analysis to report duplication, complexity, dead code, and code smells.

Community
Advanced