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.
适用对象：生活与娱乐。自动收录 · 待核查。
原作者说明节选
从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。
查看英文原文
原文涵盖的主题
- Technical Debt Auditor
- What you're scanning for
- PHASE 1 — RECONNAISSANCE
- PHASE 2 — SYSTEMATIC SCAN
- Marker debt scan
- Dead code scan
- Dependency debt scan
- Complexity hotspot scan
You are performing a systematic technical debt audit of this codebase. Your goal: produce a quantified, actionable report that tells the team exactly where their debt is, how severe it is, and what to fix first. This is not a vague "code review" — it's a structured scan with concrete metrics and a prioritized remediation plan. Technical debt is like financial debt — it accumulates interest. A quick hack today costs 10x more to fix in six months when three features depend on it. Your job is to find the debt before the interest compounds, quantify it so it can be prioritized against feature work, and give the team a realistic plan to pay it down. | Debt category | What to look for | Why it matters | |---|---|---| | Marker debt | TODO, FIXME, HACK, XXX, TEMP, WORKAROUND comments | Developers flagged these as known shortcuts — they're self-reported debt | | Dead code | Unused exports, unreachable branches, commented-out code blocks, unused files | Dead code misleads readers, adds cognitive load, and sometimes hides bugs | | Dependency debt | Outdated packages, deprecated APIs, pinned-to-old-major versions, unused deps in package manifest | Stale deps accumulate security vulns and block
这里只展示节选，请以完整原文和当前要求为准。
- 来源仓库
- davila7/claude-code-templates
- 源文件
- cli-tool/components/skills/development/technical-debt-auditor/SKILL.md
- 固定版本
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
准备条件
- 本条仅收录原作者的技能元数据；请阅读完整说明，确认依赖、许可与使用条件。
第一件可以尝试的小事
先阅读原作者说明，再决定是否在自己的 AI 工具中使用。
对应 AI 工具说明
作者有说明不等于本站实机验证。没有证据时，不自动标为兼容、安全或免费。
来源与内容状态
本条为自动发现的元数据，尚未完成人工文档核查；适用性与运行结果待核查。
原作者：davila7/claude-code-templates · 原作者仓库元数据。文档核查：未核查。最近来源检查：2026-11-09T14:01:44.826Z。
分类由名称、说明与路径规则生成，分类不代表已核实适配。
许可与权利归属
MIT。第三方内容及版权归原作者，使用条件以原文为准。
许可原文 ↗本站没有因同步、复制或用户自报成功而将资源标为运行验证通过。
限制与注意事项
- 元数据收录不代表本站已经安装、适配、实测或进行安全审查。