codebase-cleanup-tech-debt
分析並減少技術負債
此技能協助開發團隊識別、量化及優先處理程式碼庫中的技術負債。它提供結構化的方法來評估負債影響、計算修復工作的投資報酬率，以及制定可操作的計畫來逐步改善程式碼品質。
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "codebase-cleanup-tech-debt". Analyze my Ruby on Rails codebase for technical debt
النتيجة المتوقعة:
## 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
استخدام "codebase-cleanup-tech-debt". Create a debt prevention strategy for our team
النتيجة المتوقعة:
## 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
التدقيق الأمني
آمنAll 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.
الأنماط المكتشفة
درجة الجودة
ماذا يمكنك بناءه
初始負債評估
對現有程式碼庫進行全面掃描，以記錄所有技術負債、按類型分類，並根據業務影響進行優先排序。
衝刺規劃支援
識別快速成果和高投資報酬率的重構任務，以纳入 upcoming 衝刺規劃會議。
利害關係人溝通
產生執行摘要和投資報酬率預測，以向業務領導階層說明技術負債修復投資的理由。
جرّب هذه الموجهات
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.
أفضل الممارسات
- 從顯示立即投資報酬率的快速成果開始，以建立團隊對更大規模重構工作的認同
- 始終以開發人時和貨幣量化負債影響，以有效與利害關係人溝通
- 使用功能開關進行漸進式重構，以降低風險並實現增量價值交付
تجنب
- 試圖一次修復所有負債 - 根據影響和努力進行優先排序，以實現可持續的進展
- 忽視測試負債 - 低覆蓋率會加劇所有其他負債類型並減慢未來的變更
- 不追蹤負債趨勢 - 沒有指標，團隊就無法衡量改善或退步
الأسئلة المتكررة
此技能分析哪些類型的技術負債？
此技能會對我的程式碼庫進行變更嗎？
此技能如何計算負債修復的投資報酬率？
此技能可以配合任何程式語言使用嗎？
我們應該多久執行一次技術負債分析？
什麼是負債預算，我們如何實施？
تفاصيل المطور
المؤلف
sickn33الترخيص
MIT
المستودع
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/codebase-cleanup-tech-debtمرجع
main
بنية الملفات
📄 SKILL.md