This skill analyzes and prioritizes technical debt.
Main Features
- Code Complexity: Cyclomatic complexity
- Duplicate Code: Copy-paste detection
- Outdated Dependencies: dependencies that need updating
- TODO/FIXME: unresolved tasks
- Test coverage: areas with insufficient coverage
- Prioritization: evaluated by impact and cost
Example Analysis Report
# 技術的負債分析レポート
Summary
- Total Debt Score: 157 points
- Estimated Resolution Time: 8 weeks
- Critical: 3 items
- High: 12 items
- Medium: 25 items
Critical Debt (Immediate Action Required)
1. Old Node.js version (v14)
- Impact: security risk, performance degradation
- Cost: 2 days
- Priority: 🔴 Critical
- Action: Upgrade to Node.js 18
2. Insufficient test coverage (42%)
- Impact: increased bug risk
- Cost: 2 weeks
- Priority: 🔴 Critical
- Action: add tests with a target of 80% coverage
3. Vulnerable dependency (lodash 4.17.15)
- Impact: CVE-2020-8203
- Cost: 1 hour
- Priority: 🔴 Critical
- Action: npm update lodash
High Debt
Code Complexity
- File:
src/order/processor.ts - Complexity: 45 (recommended: <10)
- Cost: 3 days
- Action: Refactoring
Duplicate Code
- Locations: 15 locations
- Duplication Rate: 23%
- Cost: 1 week
- Action: consolidation
Recommended Execution Order
- Vulnerability fix (1 hour)
- Node.js upgrade (2 days)
- Refactoring Critical complex code (1 week)
- Improving test coverage (2 weeks)
- Resolving duplicate code (1 week)
## バージョン情報
- Version: 1.0.0