ponytail-audit
bydietrichgebert· 6 skills
Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.
How to install ponytail-audit?
dietrichgebert/ponytail/ponytail-audit
$npx -y skills add dietrichgebert/ponytail --skill ponytail-auditInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/dietrichgebert/ponytail" --skill "dietrichgebert/ponytail/ponytail-audit"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/dietrichgebert/ponytail" that are relevant to the current task. Run `npx skills add "https://github.com/dietrichgebert/ponytail"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank |
| 2 | findings biggest cut first. |
| 3 | |
| 4 | ## Tags |
| 5 | |
| 6 | Same as ponytail-review: |
| 7 | |
| 8 | - `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing. |
| 9 | - `stdlib:` hand-rolled thing the standard library ships. Name the function. |
| 10 | - `native:` dependency or code doing what the platform already does. Name the feature. |
| 11 | - `yagni:` abstraction with one implementation, config nobody sets, layer with one caller. |
| 12 | - `shrink:` same logic, fewer lines. Show the shorter form. |
| 13 | |
| 14 | ## Hunt |
| 15 | |
| 16 | Deps the stdlib or platform already ships, single-implementation interfaces, |
| 17 | factories with one product, wrappers that only delegate, files exporting one |
| 18 | thing, dead flags and config, hand-rolled stdlib. |
| 19 | |
| 20 | ## Output |
| 21 | |
| 22 | One line per finding, ranked: `<tag> <what to cut>. <replacement>. [path]`. |
| 23 | End with `net: -<N> lines, -<M> deps possible.` Nothing to cut: `Lean already. Ship.` |
| 24 | |
| 25 | ## Boundaries |
| 26 | |
| 27 | Scope: over-engineering and complexity only. Correctness bugs, security holes, |
| 28 | and performance are explicitly out of scope. Route them to a normal review |
| 29 | pass. Lists findings, applies nothing. One-shot. |
| 30 | "stop ponytail-audit" or "normal mode" to revert. |
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
