codebase-cleanup-tech-debt
分析和减少技术债务
这个技能帮助开发团队识别、量化和优先处理代码库中的技术债务。它提供结构化的方法来评估债务影响、计算修复工作的投资回报率，并制定可操作的计划来逐步提高代码质量。
Télécharger le ZIP du skill
Importer dans Claude
Allez dans Paramètres → Capacités → Skills → Importer un skill
Activez et commencez à utiliser
Tester
Utilisation de "codebase-cleanup-tech-debt". Analyze my Ruby on Rails codebase for technical debt
Résultat attendu:
## Technical Debt Analysis
### Key Findings
- **Critical**: 3 God classes in app/models (500+ lines each)
- **High**: 23% code duplication in validation logic
- **Medium**: Test coverage at 45% (target: 80%)
### Top Quick Wins
1. Extract duplicate validation to shared module (8 hours, saves 20 hours/month)
2. Add error monitoring to payment service (4 hours, saves 15 hours/month)
### Recommended Roadmap
- **Month 1**: Quick wins + begin OrderService refactor
- **Month 2-3**: Complete refactoring + upgrade Rails version
- **Quarter 2**: Comprehensive test coverage improvement
Utilisation de "codebase-cleanup-tech-debt". Create a debt prevention strategy for our team
Résultat attendu:
## Debt Prevention Strategy
### Automated Gates
- Pre-commit: Complexity check (max 10), duplication check (max 5%)
- CI: Dependency audit, performance regression tests
- Code Review: Two approvals, tests required, documentation required
### Debt Budget
- Allowed monthly increase: 2%
- Mandatory quarterly reduction: 5%
- Tracking tools: SonarQube, Dependabot, CodeCov
### Success Metrics
- Monthly: Debt score reduction target -5%
- Quarterly: Architecture health score, developer satisfaction
Audit de sécurité
SûrAll 30 static findings evaluated as false positives. The skill is purely instructional content for technical debt analysis. Dollar amounts in examples ($150/hour) were misidentified as shell commands. Generic technical terms were misidentified as cryptographic algorithms. Prevention planning was misidentified as system reconnaissance. No actual security risks present.
Motifs détectés
Score de qualité
Ce que vous pouvez construire
初步债务评估
对现有代码库进行全面扫描，记录所有技术债务，按类型分类，并根据业务影响进行优先级排序。
冲刺计划支持
识别快速收益和高投资回报率的 refactoring 任务，以便在即将进行的冲刺规划会议中纳入。
干系人沟通
生成执行摘要和投资回报率预测，以向业务领导层证明技术债务修复投资的合理性。
Essayez ces prompts
Analyze my codebase for technical debt. Focus on finding: duplicated code patterns, high complexity functions, missing tests, and outdated dependencies. List the top 10 debt items with estimated remediation effort.
Conduct a full technical debt audit of our codebase. Include: code debt (duplication, complexity, structure), architecture debt (design flaws, tech stack), testing debt (coverage, quality), documentation debt, and infrastructure debt. For each category, quantify the impact and create a prioritized remediation plan.
Calculate the ROI for our top 20 technical debt items. For each, estimate: developer time lost per month, bug rate impact, and onboarding delay. Rank by highest ROI opportunity and create a quarterly remediation roadmap.
Design a debt prevention strategy for our team. Include: pre-commit hooks for code quality, CI pipeline gates, code review requirements, and a debt budget policy. Explain how to track compliance and measure success.
Bonnes pratiques
- 从显示快速投资回报率的快速收益开始，以获得团队对更大 refactoring 工作的支持
- 始终用开发者小时数和货币来量化债务影响，以便有效地与利益相关者沟通
- 使用功能标志进行渐进式 refactoring，以降低风险并实现渐进式价值交付
Éviter
- 试图一次性修复所有债务 - 根据影响和工作量进行优先级排序以实现可持续进展
- 忽视测试债务 - 低覆盖率会加剧所有其他债务类型并减缓未来的更改
- 不随时间跟踪债务 - 没有指标，团队就无法衡量改进或回归
Foire aux questions
这个技能分析哪些类型的技术债务？
这个技能会更改我的代码库吗？
该技能如何计算债务修复的 ROI？
这个技能可以适用于任何编程语言吗？
我们应该多久运行一次技术债务分析？
什么是债务预算，我们如何实施它？
Détails du développeur
Auteur
sickn33Licence
MIT
Dépôt
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/codebase-cleanup-tech-debtRéf
main
Structure de fichiers
📄 SKILL.md