ponytail-debt
Skill209 starsChanged 15 days agoMITView on GitHub
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.
66 other projects use a version of this, 62 of them edited.
Adopted by
Most recently taken up by
- jjsizemore/jjskillsedited, first seen Nov 16, 2026
- mvsimao/agent-skillsedited, first seen Nov 16, 2026
- AlexanderTar/swarmrunedited, first seen Nov 16, 2026
- FAHTHIZ/oasisedited, first seen Nov 16, 2026
- ezmichaely/make-it-ezyedited, first seen Nov 15, 2026
- gladosAagman/ponytailedited, first seen Nov 15, 2026
Used with
Projects with it also use caveman-explore, caveman-discover and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JuliusBrusseeSkillcaveman-explore
Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.
Also in 5 projects that use this
JuliusBrusseeSkillcaveman-discover
Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.
Also in 3 projects that use this
huangzidaSkillcaveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Also in 6 projects that use this
huangzidaSkillcaveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Also in 9 projects that use this
ryu111Skillmigration
Migration planning expertise. Use when replacing tools/frameworks, upgrading versions, migrating databases, or planning transitions. Contains strategies, compatibility analysis methods, and rollback planning.
Also in 4 projects that use this
MicrosoftSkillcaveman
Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules
Also in 11 projects that use this
- +4 more from JuliusBrussee
- +2 more from huangzida
Other versions66 projects use a version of this.
Word for word · 0
None found.
Edited · 62
- DietrichGebert/ponytail★ 182k73% same
- kortix-ai/CompanyOS★ 21k46% same
- kortix-ai/suna★ 21k46% same
- marmelab/atomic-crm★ 1.4k46% same
- Cygnux-Labs/Tracekit★ 72671% same
- mezotv/notra★ 25646% same
- usenotra/notra★ 25646% same
- jacred-fdb/jacred★ 14046% same
- Wenaixi/dsh-ponytail★ 4646% same
- KenSuh/open-agent-harness★ 3346% same
52 more not listed
Wrote their own version · 4
- dekoza/oh-my-slop★ 4same name
- Binbin-miao/workbuddy-expert-team★ 1same name
- raditia/CraftKit★ 1same name
- lost-rob0t/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lnwjud-scheduled-continuationSkill
- ponytail-auditSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 65 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Every deliberate ponytail shortcut is marked with a shortcut: comment naming its ceiling and upgrade path (older code may say ponytail:).
- Distinctive: line 25
Add comment prefixes for the actual language when needed.
- Very specific: line 27
If the user names their own marker word (/ponytail-debt TODO), scan for that literal marker instead, escaping regex characters.
“Common” is measured: kept by at least 6 in 10 of the 65 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
For lnwjud, first read repository integration. It controls activation, source discovery, and host-specific guidance below.
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
Query CodeGraph first when .codegraph/ exists. Comment markers are not
fully represented by a symbol graph, so then scan them with rg, honoring
.gitignore and excluding Git metadata, dependencies, and build output:
rg -n --hidden --glob "!.git/**" --glob "!**/node_modules/**" --glob "!**/dist/**" --glob "!**/build/**" '(#|//|/\*) ?(shortcut|ponytail):' .Add comment prefixes for the actual language when needed.
If the user names their own marker word (/ponytail-debt TODO), scan for that literal marker instead, escaping regex characters.
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. When the user requests a saved ledger, write it to the requested path
(or PONYTAIL-DEBT.md when no path is given). A report-only request does not authorize a saved ledger. One-shot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

