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模式、技能與指令的快速參考卡。一次性顯示,非持續模式。觸發方式:/ponytail-help、「ponytail help」、「what ponytail commands」、「how do I use ponytail」。