techdebt

What it does

This skill enables AI agents to identify, analyze, and manage technical debt within software projects. It helps teams prioritize refactoring efforts by quantifying the impact of outdated code on system performance and maintainability.

When to use it

• Prioritizing Refactoring: Determine which legacy modules pose the highest risk to future development velocity.
• Resource Allocation: Justify budget or time for cleanup tasks by presenting data-driven metrics on debt accumulation.
• Architecture Reviews: Evaluate whether current codebases meet modern standards before adding new features.
• Incident Response: Quickly assess if recent bugs stem from known technical debt areas needing immediate attention.

Key capabilities

• Quantifies technical debt based on code complexity and outdated patterns.
• Correlates debt levels with potential system instability or performance bottlenecks.
• Generates actionable reports to guide engineering roadmaps.
• Integrates with existing CI/CD pipelines for continuous debt tracking.

Example prompts

• "Analyze our Java repository and list the top three areas with the highest technical debt scores."
• "Compare the technical debt of the payment service versus the user authentication module."
• "Generate a report on how accumulated tech debt is affecting our deployment frequency over the last quarter."

Tips & gotchas

Ensure your codebase includes sufficient metadata or linting rules for accurate analysis, as the skill relies on detecting specific patterns. For large monorepos, consider breaking down the analysis by service to avoid overwhelming output.