Stats
Actions
Tags
From ponytail
Scans the entire codebase for over-engineering: dead code, stdlib replacements, native alternatives, YAGNI abstractions, and bloat. Produces a ranked list of what to delete or simplify.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ponytail:ponytail-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank
ponytail-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.
Complexity only, correctness bugs, security holes, and performance go to a normal review pass. Lists findings, applies nothing. One-shot. "stop ponytail-audit" or "normal mode" to revert.
npx claudepluginhub dietrichgebert/ponytail --plugin ponytailReviews diffs for over-engineering: reinventing stdlib, unneeded deps, speculative abstractions, dead flexibility. One line per finding with suggested replacement. Complements correctness review.
Audits entire codebase for structural quality, file sprawl, thin wrappers, leaked logic, spaghetti growth, and dependency freshness via context7. Encourages code-judo simplifications.
Detects codebase bloat via progressive analysis tiers covering dead code, duplication, complexity, doc bloat, AI-generated patterns, dependencies, and git history. For maintenance, refactoring prep, and pre-release cleanup.