domains / families / software-engineering / code-refactoring-tech-debt

code-refactoring-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 inventory, impact, metrics, and remediation structure, but they disagree on how to treat the numeric examples and on scope. The antigravity copy presents the dollar/hour figures as the procedure's calculations, while the agentic-awesome copy explicitly labels them as hypothetical planning examples, forbids fabricating telemetry, and restricts review-only scope. Crowning one copy would hide the other's safety constraints and its different ROI framing.