ponytail-audit
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what…
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
Claude Code
$ npx -y skills add DietrichGebert/ponytail --skill ponytail-debt --agent claude-code
Codex
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a codex -y
Cursor
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a cursor -y
Gemini CLI
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a gemini-cli -y
GitHub Copilot
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a github-copilot -y
OpenCode
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a opencode -y
Windsurf
$ npx skills add DietrichGebert/ponytail --skill ponytail-debt -a windsurf -y
name: ponytail-debt description: > List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
Every deliberate ponytail shortcut is marked with a `shortcut:` comment naming its ceiling and upgrade path (older code may say `ponytail:`). This collects them into one ledger so a deferral can't quietly become permanent.
Grep the repo for comment markers, skipping `.git` and everything the `.gitignore` files ignore (dependencies, build output, caches, in any stack):
`git grep --no-index --exclude-standard -nE '(#|//|/[*]) ?(shortcut|ponytail):'` (add other comment prefixes if your stack uses them)
If the user names their own marker word (`/ponytail-debt TODO`), grep for that word instead.
Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger. Skip hits that are not a deferral, like a note about a keyboard shortcut.
One row per marker, grouped by file:
`<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.`
The convention is `shortcut: <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 marker 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 shortcut debt. Clean ledger.`
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.
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what…
Show ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does…
Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I…
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast…
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.