domains / families / software-engineering / codebase-cleanup-tech-debt

codebase-cleanup-tech-debt

combined

Identify and prioritize technical debt by maintenance cost, delivery impact, and risk. Use when assessing code health or planning a measurable remediation roadmap. Identify technical debt from actual code and change history, estimate its impact, and prioritize bounded improvements with explicit assumptions.

When to use

• Working on technical debt analysis and remediation tasks or workflows
• Needing guidance, best practices, or checklists for technical debt analysis and remediation

When not to use

• The task is unrelated to technical debt analysis and remediation
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core procedure (inventory, impact assessment, metrics dashboard, prioritized remediation plan) and the same example thresholds. However, the sickn33 copy adds material constraints and a different framing: it explicitly requires inspecting actual repository/change/incident history, states that the numbers and thresholds are hypothetical planning examples, forbids fabricating telemetry, and limits review-only scope from authorizing broad refactors or deployment. The rmyndharis copy lacks these guardrails and uses a generic $ARGUMENTS placeholder. Crowning one copy would hide the real alternative of a stricter, evidence-based, review-only variant, so the copies should be combined.