ponytail-debt
此技能通过扫描代码中的特定注释，将技术债快捷方式汇集到统一的债务账本中，确保这些延期处理的任务不会被遗忘。它能生成一份清晰的报告，帮助团队有效追踪和管理技术债，从而提升代码质量和项目健康度。
npx skills add https://github.com/dietrichgebert/ponytail --skill ponytail-debtBefore / After 效果对比
1 组用户/开发者需要手动在代码库中搜索或依赖记忆来追踪技术债快捷方式，这导致许多延期处理的任务被遗忘，技术债不断累积，影响项目健康。
此技能自动扫描代码并生成技术债报告，将所有快捷方式汇集到账本中，确保技术债清晰可见并得到有效管理，显著提升了追踪效率和代码质量。
Every deliberate ponytail shortcut is marked with a ponytail: comment naming
its ceiling and upgrade path. This collects them into one ledger so a deferral
can't quietly become permanent.
Scan
Grep the repo for comment markers, skipping node_modules, .git, and build
output:
grep -rnE '(#|//) ?ponytail:' . (add other comment prefixes if your stack uses them)
Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger.
Output
One row per marker, grouped by file:
<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.
The convention is ponytail: <ceiling>, <upgrade path>, so pull the ceiling
and the trigger straight from the comment. Want an owner per row too? add
git blame -L<line>,<line>.
Flag the rot risk: any ponytail: comment that names no upgrade path or
trigger gets a no-trigger tag, those are the ones that silently rot.
End with <N> markers, <M> with no trigger. Nothing found: No ponytail: debt. Clean ledger.
Boundaries
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. PONYTAIL-DEBT.md). One-shot. "stop ponytail-debt" or
"normal mode" to revert.
用户评价 (0)
发表评价
暂无评价
统计数据
用户评分
为此 Skill 评分