ponytail-audit
Skill2 starsChanged 7 days agoNo licenceView on GitHub
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.
75 other projects use a version of this, 8 of them edited; 1 of 6 edited versions we compared changed its rules; 5 new projects in the last 4 weeks, against 5 the 4 before.
How people change it
1 of 6 edited versions changed its rules.
Of the 6 edited versions we compared: 5 keep every rule, 1 made changes of their own.
Rules people drop
- Before calling code unused, grep the whole tree for it, including tests, fixtures, config, and string or dynamic references.dropped by 1 of 1
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 5 new projects took it in the last 4 weeks, 1× the 4 weeks before.thin data
Most recently taken up by
- Floppa2003/skillsedited, first seen Nov 16, 2026
- jjsizemore/jjskillstheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasisword for word, first seen Nov 16, 2026
- Yassimba/loomword for word, first seen Nov 15, 2026
- ezmichaely/make-it-ezyword for word, first seen Nov 15, 2026
- gladosAagman/ponytailedited, first seen Nov 15, 2026
Used with
Projects with it also use caveman-explore, migration 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 3 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
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 5 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 6 projects that use this
JuliusBrusseeSkillcaveman-stats
Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.
Also in 4 projects that use this
MicrosoftSkillimpeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.
Also in 9 projects that use this
- +2 more from huangzida
- +1 more from JuliusBrussee
Other versions75 projects use a version of this.
Word for word · 16
- DietrichGebert/ponytail★ 182k100% same
- Cygnux-Labs/Tracekit★ 726100% same
- Djarvur/go-ultimate★ 31100% same
- Yassimba/loom★ 13100% same
- ZerroDevs/AgentsHub-Desktop★ 9100% same
- ZerroDevs/AgentsHub★ 6100% same
- FAHTHIZ/oasis★ 4100% same
- Jay-1409/skills★ 2100% same
- qihangzhang-272/agent-skill-library★ 2100% same
- dhruvsaxena1998/skills★ 1100% same
6 more not listed
Edited · 8
- engasnm111/lnwjud★ 20993% same
- shaderera/shaderera★ 799% same
- Eclipter/agents★ 198% same
- Floppa2003/skills★ 194% same
- GabrieleDattile/agent-superpowers★ 197% same
- gladosAagman/ponytail★ 199% same
- josechifflet/setup★ 098% same
- jpc4729/setup★ 098% same
Wrote their own version · 51
- kortix-ai/CompanyOS★ 21ksame name
- kortix-ai/suna★ 21ksame name
- marmelab/atomic-crm★ 1.4ksame name
- mezotv/notra★ 256same name
- usenotra/notra★ 256same name
- jacred-fdb/jacred★ 140same name
- felipebasurto/viajante★ 56same name
- Wenaixi/dsh-ponytail★ 46same name
- KenSuh/open-agent-harness★ 33same name
- sampleXbro/agentsmesh★ 27same name
41 more not listed
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 repository9 other files it gives its agents.
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- cloud-preflight-infra-auditorSkill
- data-lineage-upstream-validatorSkill
- hybrid-impediment-investigatorSkill
- migration-spec-refinerSkill
The file
We split this skill into the rules it gives an agent
7 rules. 1 is common, 5 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 15 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 15 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.
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.

