ponytail-debt
GitHub通过扫描代码库中的ponytail注释，自动收集技术债务并生成统一账本报告。识别缺失升级路径的隐患，仅读取不修改代码，支持将结果持久化到文件，帮助追踪和防止技术债务被遗忘。
Trigger Scenarios
Install
npx skills add DietrichGebert/ponytail --skill ponytail-debt -g -y
SKILL.md
Frontmatter
{
"name": "ponytail-debt",
"license": "MIT",
"homepage": "https:\/\/github.com\/DietrichGebert\/ponytail",
"description": "Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report."
}
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.
Version History
- 40e50d9 Current 2026-07-05 15:19
