technical-debt-auditor
扫描代码库并生成量化的技术债务报告,附优先级排序的修复计划。分析死代码、TODO/FIXME/HACK 标记、依赖陈旧度、复杂度热点、代码重复信号、测试覆盖缺口、未使用的导出以及过时模式。当用户要求审计代码库的技术债务、希望对其代码质量做健康检查、说出“我应该重点重构哪里”“找出代码异味”“审计我的代码库”“我们有哪些技术债务”“为清理工作排优先级”之类的话,或询问代码质量指标时,使用此技能。当用户提到“代码腐化”“遗留代码清理”“重构优先级”,或希望在重大工作前了解项目整体健康状况时,也应触发。即使用户没有明确说“技术债务”,只要请求是系统性地评估代码质量并确定改进优先级,也属于此技能范围。
机器翻译查看英文原文
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
适用对象:生活与娱乐。自动收录 · 待核查。
在 Cursor 中使用
该组合的专门教程待补充,尚未核实适配。
准备条件
- 本条仅收录原作者的技能元数据;请阅读完整说明,确认依赖、许可与使用条件。
选择已有说明的 AI 工具,或在页面加载后保存待办及提出教程请求。
查看原作者说明 ↗