Identify and prioritize technical debt across codebases with impact, risk, and effort scores.
npx skills add https://github.com/mmahalwy/cooper --skill tech-debt-mmahalwy
Please help me install this Agent Skill. Skill: tech-debt Source: https://github.com/mmahalwy/cooper/tree/main/.agents/skills/tech-debt Command: npx skills add https://github.com/mmahalwy/cooper --skill tech-debt-mmahalwy
Systematically identify and reduce technical debt that slows development, introduces bugs, and increases maintenance costs across code, architecture, tests, dependencies, documentation, and infrastructure.
Audit the repository for technical debt and return a prioritized remediation list with impact, risk, and effort estimates plus a phased plan ready for sprint planning.
High-intent search queries and answers about installing and using this skill.
Prioritize technical debt by scoring items across code, architecture, tests, dependencies, and infrastructure using a formula of (Impact + Risk) x (6 - Effort) to rank remediation work. This generates a prioritized list with business justifications.
Auditing a legacy monolith involves categorizing debt into code, architecture, test, dependency, documentation, and infrastructure debt. The audit returns concrete examples, associated risks, and a phased remediation plan suitable for sprint planning.
Triage a maintenance backlog by evaluating each item's impact, risk, and estimated effort. The process calculates a priority score and produces a phased remediation plan with business justifications ready for sprint-based delivery.
Yes, you can plan dependency upgrades and infrastructure hardening by classifying them as dependency and infrastructure debt. The framework scores each item by impact, risk, and effort to create a phased remediation plan.
You need a technical debt audit when development slows, bugs increase, or maintenance costs rise across your codebase. It systematically identifies debt in tests, dependencies, documentation, architecture, and infrastructure to guide remediation.
Yes, the technical debt remediation process applies to software engineering teams conducting code quality audits, refactoring planning, and maintenance backlog triage on repositories and systems of varying scale.
mattphanmRefactor code safely with baseline tests and incremental validation.
vndkubiIdentify and prioritize technical debt with effort estimates and business impact.
NoobyGainsEnforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.
VictorSmaniottoAnalyze PHP code for smells, complexity, duplications, and pattern violations.
