jaktestowac/awesome-copilot-for-testers / plugins/tech-debt-analysis/skills/tech-debt-analysis
tech-debt-analysis
VerifiedAnalyzes technical debt in codebases, test suites, architecture, dependencies, and delivery workflows using observable signals. Use when auditing repository health, explaining slow delivery or flaky tests, prioritizing refactoring, or building an evidence-based remediation roadmap with risk, effort, and ROI. Use when user asks for technical debt analysis, repository audit, or refactor planning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.5 KB |
| resources/debt-taxonomy.md | markdown | 4.9 KB |
| resources/example-technical-debt-report.md | markdown | 6.0 KB |
| resources/prioritization-matrix.md | markdown | 2.8 KB |
| resources/technical-debt-report-template.md | markdown | 3.1 KB |
| resources/test-debt-catalogue.md | markdown | 3.5 KB |
resources/prioritization-matrix.md
View on GitHub# Prioritization Matrix
Use this rubric to keep debt scoring consistent.
The goal is not mathematical precision; the goal is disciplined prioritization.
## 1. Severity
| Level | Meaning | Typical signal |
| --- | --- | --- |
| **S1** | Actively dangerous or blocking | security exposure, tests that cannot fail meaningfully, architecture preventing delivery |
| **S2** | Major drag on quality or velocity | recurring flaky suite, repeated regression source, blocked upgrade path |
| **S3** | Noticeable friction | duplication, awkward abstractions, repeated manual work |
| **S4** | Minor or cosmetic | low-risk cleanup that improves clarity but not delivery materially |
## 2. Risk of Remediation
| Level | Meaning | Typical characteristics |
| --- | --- | --- |
| **Low** | Safe, localized change | isolated module, good test safety net, small blast radius |
| **Medium** | Some coordination required | shared module, partial regression risk, moderate coupling |
| **High** | Non-trivial blast radius | cross-cutting refactor, behavioral uncertainty, weak test safety |
## 3. Effort
| Level | Meaning |
| --- | --- |
| **XS** | Minutes to a couple of hours |
| **S** | Small change set, usually within one PR |
| **M** | Multi-file change or some coordination |
| **L** | Multi-step effort across several areas |
| **XL** | Strategic initiative or staged program of work |
## 4. ROI
| Level | Meaning |
| --- | --- |
| **Low** | Nice cleanup, but modest business or engineering value |
| **Medium** | Meaningful reduction in friction, bugs, or maintenance cost |
| **High** | Major reduction in delivery drag, production risk, or test unreliability |
## 5. Time Horizon
| Level | Meaning |
| --- | --- |
| **Tactical** | Days |
| **Short-term** | Weeks |
| **Strategic** | Months |
## 6. Decision Buckets
| Bucket | When to use |
| --- | --- |
| **Fix Now** | High current cost or risk, and deferring is more dangerous than acting |
| **Fix Soon** | Important, but needs prep work, better timing, or more evidence |
| **Accept for Now** | Known debt, consciously deferred with rationale and revisit trigger |
## Practical heuristics
- **High ROI + Low/Medium effort** usually means quick win.
- **High severity + High remediation risk** usually needs staged work, not avoidance.
- **Low severity + High effort** is often a defer candidate unless it unlocks other work.
- **Test debt with high flakiness cost** should often be prioritized ahead of cosmetic code cleanup.
- **Blocked upgrades** often deserve more priority than they first appear because the cost compounds over time.
## Suggested sorting order
When presenting the debt register, sort primarily by:
1. severity
2. business or delivery impact
3. ROI
4. effort
This keeps the report focused on the most consequential debt, not merely the easiest cleanup.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |