mcpbeat

Ponytail Debt

dietrichgebert/ponytail-debt

Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

374 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
94770
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/DietrichGebert/ponytail --skill ponytail-debt

The instruction itself

3 sections, as written by the author

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.

Repackaged in 1 other repositories

same content, different owner
0xwilliamortiz/ponytail-improved open on GitHub →

How to use it

Copy the folder

Take dietrichgebert/ponytail-debt from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.