[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CJ2QCJYWNWCAGAC342R162":3,"skill-same:01M7CJ2QCJYWNWCAGAC342R162":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CJ2QCJYWNWCAGAC342R162","codebase-cleanup-tech-debt",null,"You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fcodebase-cleanup-tech-debt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: codebase-cleanup-tech-debt\ndescription: \"You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Technical Debt Analysis and Remediation\n\nYou are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.\n\n## Use this skill when\n\n- Working on technical debt analysis and remediation tasks or workflows\n- Needing guidance, best practices, or checklists for technical debt analysis and remediation\n\n## Do not use this skill when\n\n- The task is unrelated to technical debt analysis and remediation\n- You need a different domain or tool outside this scope\n\n## Context\nThe user needs a comprehensive technical debt analysis to understand what's slowing down development, increasing bugs, and creating maintenance challenges. Focus on practical, measurable improvements with clear ROI.\n\n## Requirements\n$ARGUMENTS\n\n## Instructions\n\n### 1. Technical Debt Inventory\n\nConduct a thorough scan for all types of technical debt:\n\n**Code Debt**\n- **Duplicated Code**\n  - Exact duplicates (copy-paste)\n  - Similar logic patterns\n  - Repeated business rules\n  - Quantify: Lines duplicated, locations\n  \n- **Complex Code**\n  - High cyclomatic complexity (>10)\n  - Deeply nested conditionals (>3 levels)\n  - Long methods (>50 lines)\n  - God classes (>500 lines, >20 methods)\n  - Quantify: Complexity scores, hotspots\n\n- **Poor Structure**\n  - Circular dependencies\n  - Inappropriate intimacy between classes\n  - Feature envy (methods using other class data)\n  - Shotgun surgery patterns\n  - Quantify: Coupling metrics, change frequency\n\n**Architecture Debt**\n- **Design Flaws**\n  - Missing abstractions\n  - Leaky abstractions\n  - Violated architectural boundaries\n  - Monolithic components\n  - Quantify: Component size, dependency violations\n\n- **Technology Debt**\n  - Outdated frameworks\u002Flibraries\n  - Deprecated API usage\n  - Legacy patterns (e.g., callbacks vs promises)\n  - Unsupported dependencies\n  - Quantify: Version lag, security vulnerabilities\n\n**Testing Debt**\n- **Coverage Gaps**\n  - Untested code paths\n  - Missing edge cases\n  - No integration tests\n  - Lack of performance tests\n  - Quantify: Coverage %, critical paths untested\n\n- **Test Quality**\n  - Brittle tests (environment-dependent)\n  - Slow test suites\n  - Flaky tests\n  - No test documentation\n  - Quantify: Test runtime, failure rate\n\n**Documentation Debt**\n- **Missing Documentation**\n  - No API documentation\n  - Undocumented complex logic\n  - Missing architecture diagrams\n  - No onboarding guides\n  - Quantify: Undocumented public APIs\n\n**Infrastructure Debt**\n- **Deployment Issues**\n  - Manual deployment steps\n  - No rollback procedures\n  - Missing monitoring\n  - No performance baselines\n  - Quantify: Deployment time, failure rate\n\n### 2. Impact Assessment\n\nCalculate the real cost of each debt item:\n\n**Development Velocity Impact**\n```\nDebt Item: Duplicate user validation logic\nLocations: 5 files\nTime Impact: \n- 2 hours per bug fix (must fix in 5 places)\n- 4 hours per feature change\n- Monthly impact: ~20 hours\nAnnual Cost: 240 hours × $150\u002Fhour = $36,000\n```\n\n**Quality Impact**\n```\nDebt Item: No integration tests for payment flow\nBug Rate: 3 production bugs\u002Fmonth\nAverage Bug Cost:\n- Investigation: 4 hours\n- Fix: 2 hours  \n- Testing: 2 hours\n- Deployment: 1 hour\nMonthly Cost: 3 bugs × 9 hours × $150 = $4,050\nAnnual Cost: $48,600\n```\n\n**Risk Assessment**\n- **Critical**: Security vulnerabilities, data loss risk\n- **High**: Performance degradation, frequent outages\n- **Medium**: Developer frustration, slow feature delivery\n- **Low**: Code style issues, minor inefficiencies\n\n### 3. Debt Metrics Dashboard\n\nCreate measurable KPIs:\n\n**Code Quality Metrics**\n```yaml\nMetrics:\n  cyclomatic_complexity:\n    current: 15.2\n    target: 10.0\n    files_above_threshold: 45\n    \n  code_duplication:\n    percentage: 23%\n    target: 5%\n    duplication_hotspots:\n      - src\u002Fvalidation: 850 lines\n      - src\u002Fapi\u002Fhandlers: 620 lines\n      \n  test_coverage:\n    unit: 45%\n    integration: 12%\n    e2e: 5%\n    target: 80% \u002F 60% \u002F 30%\n    \n  dependency_health:\n    outdated_major: 12\n    outdated_minor: 34\n    security_vulnerabilities: 7\n    deprecated_apis: 15\n```\n\n**Trend Analysis**\n```python\ndebt_trends = {\n    \"2024_Q1\": {\"score\": 750, \"items\": 125},\n    \"2024_Q2\": {\"score\": 820, \"items\": 142},\n    \"2024_Q3\": {\"score\": 890, \"items\": 156},\n    \"growth_rate\": \"18% quarterly\",\n    \"projection\": \"1200 by 2025_Q1 without intervention\"\n}\n```\n\n### 4. Prioritized Remediation Plan\n\nCreate an actionable roadmap based on ROI:\n\n**Quick Wins (High Value, Low Effort)**\nWeek 1-2:\n```\n1. Extract duplicate validation logic to shared module\n   Effort: 8 hours\n   Savings: 20 hours\u002Fmonth\n   ROI: 250% in first month\n\n2. Add error monitoring to payment service\n   Effort: 4 hours\n   Savings: 15 hours\u002Fmonth debugging\n   ROI: 375% in first month\n\n3. Automate deployment script\n   Effort: 12 hours\n   Savings: 2 hours\u002Fdeployment × 20 deploys\u002Fmonth\n   ROI: 333% in first month\n```\n\n**Medium-Term Improvements (Month 1-3)**\n```\n1. Refactor OrderService (God class)\n   - Split into 4 focused services\n   - Add comprehensive tests\n   - Create clear interfaces\n   Effort: 60 hours\n   Savings: 30 hours\u002Fmonth maintenance\n   ROI: Positive after 2 months\n\n2. Upgrade React 16 → 18\n   - Update component patterns\n   - Migrate to hooks\n   - Fix breaking changes\n   Effort: 80 hours  \n   Benefits: Performance +30%, Better DX\n   ROI: Positive after 3 months\n```\n\n**Long-Term Initiatives (Quarter 2-4)**\n```\n1. Implement Domain-Driven Design\n   - Define bounded contexts\n   - Create domain models\n   - Establish clear boundaries\n   Effort: 200 hours\n   Benefits: 50% reduction in coupling\n   ROI: Positive after 6 months\n\n2. Comprehensive Test Suite\n   - Unit: 80% coverage\n   - Integration: 60% coverage\n   - E2E: Critical paths\n   Effort: 300 hours\n   Benefits: 70% reduction in bugs\n   ROI: Positive after 4 months\n```\n\n### 5. Implementation Strategy\n\n**Incremental Refactoring**\n```python\n# Phase 1: Add facade over legacy code\nclass PaymentFacade:\n    def __init__(self):\n        self.legacy_processor = LegacyPaymentProcessor()\n    \n    def process_payment(self, order):\n        # New clean interface\n        return self.legacy_processor.doPayment(order.to_legacy())\n\n# Phase 2: Implement new service alongside\nclass PaymentService:\n    def process_payment(self, order):\n        # Clean implementation\n        pass\n\n# Phase 3: Gradual migration\nclass PaymentFacade:\n    def __init__(self):\n        self.new_service = PaymentService()\n        self.legacy = LegacyPaymentProcessor()\n        \n    def process_payment(self, order):\n        if feature_flag(\"use_new_payment\"):\n            return self.new_service.process_payment(order)\n        return self.legacy.doPayment(order.to_legacy())\n```\n\n**Team Allocation**\n```yaml\nDebt_Reduction_Team:\n  dedicated_time: \"20% sprint capacity\"\n  \n  roles:\n    - tech_lead: \"Architecture decisions\"\n    - senior_dev: \"Complex refactoring\"  \n    - dev: \"Testing and documentation\"\n    \n  sprint_goals:\n    - sprint_1: \"Quick wins completed\"\n    - sprint_2: \"God class refactoring started\"\n    - sprint_3: \"Test coverage >60%\"\n```\n\n### 6. Prevention Strategy\n\nImplement gates to prevent new debt:\n\n**Automated Quality Gates**\n```yaml\npre_commit_hooks:\n  - complexity_check: \"max 10\"\n  - duplication_check: \"max 5%\"\n  - test_coverage: \"min 80% for new code\"\n  \nci_pipeline:\n  - dependency_audit: \"no high vulnerabilities\"\n  - performance_test: \"no regression >10%\"\n  - architecture_check: \"no new violations\"\n  \ncode_review:\n  - requires_two_approvals: true\n  - must_include_tests: true\n  - documentation_required: true\n```\n\n**Debt Budget**\n```python\ndebt_budget = {\n    \"allowed_monthly_increase\": \"2%\",\n    \"mandatory_reduction\": \"5% per quarter\",\n    \"tracking\": {\n        \"complexity\": \"sonarqube\",\n        \"dependencies\": \"dependabot\",\n        \"coverage\": \"codecov\"\n    }\n}\n```\n\n### 7. Communication Plan\n\n**Stakeholder Reports**\n```markdown\n## Executive Summary\n- Current debt score: 890 (High)\n- Monthly velocity loss: 35%\n- Bug rate increase: 45%\n- Recommended investment: 500 hours\n- Expected ROI: 280% over 12 months\n\n## Key Risks\n1. Payment system: 3 critical vulnerabilities\n2. Data layer: No backup strategy\n3. API: Rate limiting not implemented\n\n## Proposed Actions\n1. Immediate: Security patches (this week)\n2. Short-term: Core refactoring (1 month)\n3. Long-term: Architecture modernization (6 months)\n```\n\n**Developer Documentation**\n```markdown\n## Refactoring Guide\n1. Always maintain backward compatibility\n2. Write tests before refactoring\n3. Use feature flags for gradual rollout\n4. Document architectural decisions\n5. Measure impact with metrics\n\n## Code Standards\n- Complexity limit: 10\n- Method length: 20 lines\n- Class length: 200 lines\n- Test coverage: 80%\n- Documentation: All public APIs\n```\n\n### 8. Success Metrics\n\nTrack progress with clear KPIs:\n\n**Monthly Metrics**\n- Debt score reduction: Target -5%\n- New bug rate: Target -20%\n- Deployment frequency: Target +50%\n- Lead time: Target -30%\n- Test coverage: Target +10%\n\n**Quarterly Reviews**\n- Architecture health score\n- Developer satisfaction survey\n- Performance benchmarks\n- Security audit results\n- Cost savings achieved\n\n## Output Format\n\n1. **Debt Inventory**: Comprehensive list categorized by type with metrics\n2. **Impact Analysis**: Cost calculations and risk assessments\n3. **Prioritized Roadmap**: Quarter-by-quarter plan with clear deliverables\n4. **Quick Wins**: Immediate actions for this sprint\n5. **Implementation Guide**: Step-by-step refactoring strategies\n6. **Prevention Plan**: Processes to avoid accumulating new debt\n7. **ROI Projections**: Expected returns on debt reduction investment\n\nFocus on delivering measurable improvements that directly impact development velocity, system reliability, and team morale.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Technical Debt Analysis and Remediation\n\nYou are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.\n\n## Use this skill when\n\n- Working on technical debt analysis and remediation tasks or workflows\n- Needing guidance, best practices, or checklists for technical debt analysis and remediation\n\n## Do not use this skill when\n\n- The task is unrelated to technical debt analysis and remediation\n- You need a different domain or tool outside this scope\n\n## Context\nThe user needs a comprehensive technical debt analysis to understand what's slowing down development, increasing bugs, and creating maintenance challenges. Focus on practical, measurable improvements with clear ROI.\n\n## Requirements\n$ARGUMENTS\n\n## Instructions\n\n### 1. Technical Debt Inventory\n\nConduct a thorough scan for all types of technical debt:\n\n**Code Debt**\n- **Duplicated Code**\n  - Exact duplicates (copy-paste)\n  - Similar logic patterns\n  - Repeated business rules\n  - Quantify: Lines duplicated, locations\n  \n- **Complex Code**\n  - High cyclomatic complexity (>10)\n  - Deeply nested conditionals (>3 levels)\n  - Long methods (>50 lines)\n  - God classes (>500 lines, >20 methods)\n  - Quantify: Complexity scores, hotspots\n\n- **Poor Structure**\n  - Circular dependencies\n  - Inappropriate intimacy between classes\n  - Feature envy (methods using other class data)\n  - Shotgun surgery patterns\n  - Quantify: Coupling metrics, change frequency\n\n**Architecture Debt**\n- **Design Flaws**\n  - Missing abstractions\n  - Leaky abstractions\n  - Violated architectural boundaries\n  - Monolithic components\n  - Quantify: Component size, dependency violations\n\n- **Technology Debt**\n  - Outdated frameworks\u002Flibraries\n  - Deprecated API usage\n  - Legacy patterns (e.g., callbacks vs promises)\n  - Unsupported dependencies\n  - Quantify: Version lag, security vulnerabilities\n\n**Testing Debt**\n- **Coverage Gaps**\n  - Untested code paths\n  - Missing edge cases\n  - No integration tests\n  - Lack of performance tests\n  - Quantify: Coverage %, critical paths untested\n\n- **Test Quality**\n  - Brittle tests (environment-dependent)\n  - Slow test suites\n  - Flaky tests\n  - No test documentation\n  - Quantify: Test runtime, failure rate\n\n**Documentation Debt**\n- **Missing Documentation**\n  - No API documentation\n  - Undocumented complex logic\n  - Missing architecture diagrams\n  - No onboarding guides\n  - Quantify: Undocumented public APIs\n\n**Infrastructure Debt**\n- **Deployment Issues**\n  - Manual deployment steps\n  - No rollback procedures\n  - Missing monitoring\n  - No performance baselines\n  - Quantify: Deployment time, failure rate\n\n### 2. Impact Assessment\n\nCalculate the real cost of each debt item:\n\n**Development Velocity Impact**\n```\nDebt Item: Duplicate user validation logic\nLocations: 5 files\nTime Impact: \n- 2 hours per bug fix (must fix in 5 places)\n- 4 hours per feature change\n- Monthly impact: ~20 hours\nAnnual Cost: 240 hours × $150\u002Fhour = $36,000\n```\n\n**Quality Impact**\n```\nDebt Item: No integration tests for payment flow\nBug Rate: 3 production bugs\u002Fmonth\nAverage Bug Cost:\n- Investigation: 4 hours\n- Fix: 2 hours  \n- Testing: 2 hours\n- Deployment: 1 hour\nMonthly Cost: 3 bugs × 9 hours × $150 = $4,050\nAnnual Cost: $48,600\n```\n\n**Risk Assessment**\n- **Critical**: Security vulnerabilities, data loss risk\n- **High**: Performance degradation, frequent outages\n- **Medium**: Developer frustration, slow feature delivery\n- **Low**: Code style issues, minor inefficiencies\n\n### 3. Debt Metrics Dashboard\n\nCreate measurable KPIs:\n\n**Code Quality Metrics**\n```yaml\nMetrics:\n  cyclomatic_complexity:\n    current: 15.2\n    target: 10.0\n    files_above_threshold: 45\n    \n  code_duplication:\n    percentage: 23%\n    target: 5%\n    duplication_hotspots:\n      - src\u002Fvalidation: 850 lines\n      - src\u002Fapi\u002Fhandlers: 620 lines\n      \n  test_coverage:\n    unit: 45%\n    integration: 12%\n    e2e: 5%\n    target: 80% \u002F 60% \u002F 30%\n    \n  dependency_health:\n    outdated_major: 12\n    outdated_minor: 34\n    security_vulnerabilities: 7\n    deprecated_apis: 15\n```\n\n**Trend Analysis**\n```python\ndebt_trends = {\n    \"2024_Q1\": {\"score\": 750, \"items\": 125},\n    \"2024_Q2\": {\"score\": 820, \"items\": 142},\n    \"2024_Q3\": {\"score\": 890, \"items\": 156},\n    \"growth_rate\": \"18% quarterly\",\n    \"projection\": \"1200 by 2025_Q1 without intervention\"\n}\n```\n\n### 4. Prioritized Remediation Plan\n\nCreate an actionable roadmap based on ROI:\n\n**Quick Wins (High Value, Low Effort)**\nWeek 1-2:\n```\n1. Extract duplicate validation logic to shared module\n   Effort: 8 hours\n   Savings: 20 hours\u002Fmonth\n   ROI: 250% in first month\n\n2. Add error monitoring to payment service\n   Effort: 4 hours\n   Savings: 15 hours\u002Fmonth debugging\n   ROI: 375% in first month\n\n3. Automate deployment script\n   Effort: 12 hours\n   Savings: 2 hours\u002Fdeployment × 20 deploys\u002Fmonth\n   ROI: 333% in first month\n```\n\n**Medium-Term Improvements (Month 1-3)**\n```\n1. Refactor OrderService (God class)\n   - Split into 4 focused services\n   - Add comprehensive tests\n   - Create clear interfaces\n   Effort: 60 hours\n   Savings: 30 hours\u002Fmonth maintenance\n   ROI: Positive after 2 months\n\n2. Upgrade React 16 → 18\n   - Update component patterns\n   - Migrate to hooks\n   - Fix breaking changes\n   Effort: 80 hours  \n   Benefits: Performance +30%, Better DX\n   ROI: Positive after 3 months\n```\n\n**Long-Term Initiatives (Quarter 2-4)**\n```\n1. Implement Domain-Driven Design\n   - Define bounded contexts\n   - Create domain models\n   - Establish clear boundaries\n   Effort: 200 hours\n   Benefits: 50% reduction in coupling\n   ROI: Positive after 6 months\n\n2. Comprehensive Test Suite\n   - Unit: 80% coverage\n   - Integration: 60% coverage\n   - E2E: Critical paths\n   Effort: 300 hours\n   Benefits: 70% reduction in bugs\n   ROI: Positive after 4 months\n```\n\n### 5. Implementation Strategy\n\n**Incremental Refactoring**\n```python\n# Phase 1: Add facade over legacy code\nclass PaymentFacade:\n    def __init__(self):\n        self.legacy_processor = LegacyPaymentProcessor()\n    \n    def process_payment(self, order):\n        # New clean interface\n        return self.legacy_processor.doPayment(order.to_legacy())\n\n# Phase 2: Implement new service alongside\nclass PaymentService:\n    def process_payment(self, order):\n        # Clean implementation\n        pass\n\n# Phase 3: Gradual migration\nclass PaymentFacade:\n    def __init__(self):\n        self.new_service = PaymentService()\n        self.legacy = LegacyPaymentProcessor()\n        \n    def process_payment(self, order):\n        if feature_flag(\"use_new_payment\"):\n            return self.new_service.process_payment(order)\n        return self.legacy.doPayment(order.to_legacy())\n```\n\n**Team Allocation**\n```yaml\nDebt_Reduction_Team:\n  dedicated_time: \"20% sprint capacity\"\n  \n  roles:\n    - tech_lead: \"Architecture decisions\"\n    - senior_dev: \"Complex refactoring\"  \n    - dev: \"Testing and documentation\"\n    \n  sprint_goals:\n    - sprint_1: \"Quick wins completed\"\n    - sprint_2: \"God class refactoring started\"\n    - sprint_3: \"Test coverage >60%\"\n```\n\n### 6. Prevention Strategy\n\nImplement gates to prevent new debt:\n\n**Automated Quality Gates**\n```yaml\npre_commit_hooks:\n  - complexity_check: \"max 10\"\n  - duplication_check: \"max 5%\"\n  - test_coverage: \"min 80% for new code\"\n  \nci_pipeline:\n  - dependency_audit: \"no high vulnerabilities\"\n  - performance_test: \"no regression >10%\"\n  - architecture_check: \"no new violations\"\n  \ncode_review:\n  - requires_two_approvals: true\n  - must_include_tests: true\n  - documentation_required: true\n```\n\n**Debt Budget**\n```python\ndebt_budget = {\n    \"allowed_monthly_increase\": \"2%\",\n    \"mandatory_reduction\": \"5% per quarter\",\n    \"tracking\": {\n        \"complexity\": \"sonarqube\",\n        \"dependencies\": \"dependabot\",\n        \"coverage\": \"codecov\"\n    }\n}\n```\n\n### 7. Communication Plan\n\n**Stakeholder Reports**\n```markdown\n## Executive Summary\n- Current debt score: 890 (High)\n- Monthly velocity loss: 35%\n- Bug rate increase: 45%\n- Recommended investment: 500 hours\n- Expected ROI: 280% over 12 months\n\n## Key Risks\n1. Payment system: 3 critical vulnerabilities\n2. Data layer: No backup strategy\n3. API: Rate limiting not implemented\n\n## Proposed Actions\n1. Immediate: Security patches (this week)\n2. Short-term: Core refactoring (1 month)\n3. Long-term: Architecture modernization (6 months)\n```\n\n**Developer Documentation**\n```markdown\n## Refactoring Guide\n1. Always maintain backward compatibility\n2. Write tests before refactoring\n3. Use feature flags for gradual rollout\n4. Document architectural decisions\n5. Measure impact with metrics\n\n## Code Standards\n- Complexity limit: 10\n- Method length: 20 lines\n- Class length: 200 lines\n- Test coverage: 80%\n- Documentation: All public APIs\n```\n\n### 8. Success Metrics\n\nTrack progress with clear KPIs:\n\n**Monthly Metrics**\n- Debt score reduction: Target -5%\n- New bug rate: Target -20%\n- Deployment frequency: Target +50%\n- Lead time: Target -30%\n- Test coverage: Target +10%\n\n**Quarterly Reviews**\n- Architecture health score\n- Developer satisfaction survey\n- Performance benchmarks\n- Security audit results\n- Cost savings achieved\n\n## Output Format\n\n1. **Debt Inventory**: Comprehensive list categorized by type with metrics\n2. **Impact Analysis**: Cost calculations and risk assessments\n3. **Prioritized Roadmap**: Quarter-by-quarter plan with clear deliverables\n4. **Quick Wins**: Immediate actions for this sprint\n5. **Implementation Guide**: Step-by-step refactoring strategies\n6. **Prevention Plan**: Processes to avoid accumulating new debt\n7. **ROI Projections**: Expected returns on debt reduction investment\n\nFocus on delivering measurable improvements that directly impact development velocity, system reliability, and team morale.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fcodebase-cleanup-tech-debt",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill codebase-cleanup-tech-debt",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill codebase-cleanup-tech-debt",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill codebase-cleanup-tech-debt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fcodebase-cleanup-tech-debt\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]