google/ponytail-audit
> Whole-repo audit for over-engineering. Like ponytail-review, but scans the or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.
This is a copy. The original lives at dietrichgebert/ponytail-ponytail-audit.
npx skills add https://github.com/google/tf-remote-vars --skill ponytail-auditponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank
findings biggest cut first.
Same as ponytail-review:
delete: dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib: hand-rolled thing the standard library ships. Name the function.native: dependency or code doing what the platform already does. Name the feature.yagni: abstraction with one implementation, config nobody sets, layer with one caller.shrink: same logic, fewer lines. Show the shorter form.Deps the stdlib or platform already ships, single-implementation interfaces,
factories with one product, wrappers that only delegate, files exporting one
thing, dead flags and config, hand-rolled stdlib.
One line per finding, ranked: <tag> <what to cut>. <replacement>. [path].
End with net: -<N> lines, -<M> deps possible. Nothing to cut: Lean already. Ship.
Scope: over-engineering and complexity only. Correctness bugs, security holes,
and performance are explicitly out of scope. Route them to a normal review
pass. Lists findings, applies nothing. One-shot.
"stop ponytail-audit" or "normal mode" to revert.
Take google/ponytail-audit from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.