ponytail-debt

作者: dietrichgebert

Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.

npx skills add https://github.com/dietrichgebert/ponytail --skill ponytail-debt

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.

来自 dietrichgebert 的更多技能

ponytail
dietrichgebert
强制采用实际可行的最懒方案,追求最简单、最短、最精简。模拟资深开发者的思维:质疑任务是否真的需要存在(YAGNI),优先使用标准库而非自定义代码,优先使用平台原生功能而非依赖项,优先用一行代码而非五十行。支持强度级别:轻量、完整(默认)、极致。当用户提及"ponytail"、"be lazy"、"lazy mode"、"simplest solution"、"minimal solution"、"yagni"、"do less"等关键词时启用。
developmentcode-review
ponytail-review
dietrichgebert
仅关注过度工程的代码审查。找出可删除的内容:重新发明的标准库、不必要的依赖、推测性抽象、无用的灵活性。每个发现一行:位置、要删除的内容、替代方案。当用户说“审查过度工程”、“可以删除什么”、“这是否过度工程”、“简化审查”或调用/ponytail-review时使用。补充以正确性为重点的审查,此审查仅追踪复杂性。
code-reviewdevelopment
ponytail-audit
dietrichgebert
对整个仓库进行过度工程审计。类似ponytail-review,但扫描整个代码库而非差异:生成一个排序列表,列出应删除、简化或替换为标准库/原生等价物的内容。当用户说“审计此代码库”、“审计过度工程”、“此仓库中可删除什么”、“查找臃肿”、“ponytail-audit”或“/ponytail-audit”时使用。一次性报告,不应用修复。
code-reviewdevelopment
ponytail-help
dietrichgebert
所有马尾辫模式、技能和命令的快速参考卡。一次性显示,非持久模式。触发方式:/ponytail-help、“ponytail help”、“what ponytail commands”、“how do I use ponytail”。