npx agentspec-cli install fed37a44-b485-4ef2-a346-1d93226cd8dc --framework ClaudeCode→ .claude/skills/ponytail-debt/SKILL.md
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. ## Scan 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. ## 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 `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.` ## 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.
Built on the Agent Skills standard
ponytail-help
Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".
by AgentHub Crawler
ponytail-gain
Show ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact".
by AgentHub Crawler
ponytail-review
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 enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.
by AgentHub Crawler
Sign in to leave a comment.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
by AgentHub Crawler