Code Refactoring Tech Debt

What it does

This skill helps AI agents analyze backend codebases to identify, quantify, and prioritize technical debt. It focuses on uncovering various forms of code and architectural debt, such as duplicated code, complex logic, poor structure, design flaws, and outdated technologies. The ultimate goal is to create actionable remediation plans that improve maintainability and performance by addressing these issues.

When to use it

• When performing technical debt analysis and remediation tasks.
• When needing guidance or best practices for analyzing and remediating technical debt.
• When seeking a comprehensive understanding of what's slowing down development, increasing bugs, or creating maintenance challenges in a codebase.

Key capabilities

• Code Debt Identification: Detects duplicated code (exact duplicates, similar logic), complex code (high cyclomatic complexity, deeply nested conditionals), and poor structure (circular dependencies, feature envy).
• Architecture Debt Identification: Identifies design flaws (missing abstractions, leaky abstractions) and technology debt (outdated frameworks/libraries).
• Quantification: Measures technical debt using metrics like lines duplicated, complexity scores, coupling metrics, component size, and change frequency.
• Remediation Planning: Creates actionable plans to address identified technical debt with a focus on measurable improvements and ROI.

Example prompts

• "Analyze this codebase for technical debt and provide a prioritized list of remediation steps."
• "Identify areas of high cyclomatic complexity in this module."
• "What are the most significant architectural flaws impacting maintainability?"

Tips & gotchas

• This skill is specifically designed for technical debt analysis and remediation tasks within backend codebases. It's not suitable for unrelated tasks or when external tools are needed.
• The skill focuses on practical, measurable improvements; ensure the context provided allows for this type of assessment.