Ponytail audit skill

Whole-repo audit for over-engineering.

by DietrichGebert·MIT license·★ 153,538 Stars on the repo·GitHub ↗

Use now

Files of Ponytail audit

DietrichGebert/main1 file shown
SKILL.md
Show the full text46 lines
ponytail-audit-2/SKILL.md46 lines · 1.9 KB

ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank findings biggest cut first.

Tags

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.
  • reuse: equivalent helper, util, or pattern already in this repo. Name the path.
  • yagni: abstraction with one implementation, config nobody sets, layer with one caller.
  • shrink: same logic, fewer lines. Show the shorter form.

Hunt

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, helpers duplicating an equivalent that already lives in this repo. Before emitting delete:, grep the whole tree for the symbol, including tests, fixtures and string or dynamic references.

Output

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.

Boundaries

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.

1---
2name: ponytail-audit
3description: >
4 Whole-repo audit for over-engineering. Like ponytail-review, but scans the
5 entire codebase instead of a diff: a ranked list of what to delete, simplify,
6 or replace with stdlib/native equivalents. Use when the user says "audit this
7 codebase", "audit for over-engineering", "what can I delete from this repo",
8 "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does
9 not apply fixes.
10---
11 
12ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank
13findings biggest cut first.
14 
15## Tags
16 
17Same as ponytail-review:
18 
19- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
20- `stdlib:` hand-rolled thing the standard library ships. Name the function.
21- `native:` dependency or code doing what the platform already does. Name the feature.
22- `reuse:` equivalent helper, util, or pattern already in this repo. Name the path.
23- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
24- `shrink:` same logic, fewer lines. Show the shorter form.
25 
26## Hunt
27 
28Deps the stdlib or platform already ships, single-implementation interfaces,
29factories with one product, wrappers that only delegate, files exporting one
30thing, dead flags and config, hand-rolled stdlib, helpers duplicating an
31equivalent that already lives in this repo.
32Before emitting `delete:`, grep the whole tree for the symbol, including tests,
33fixtures and string or dynamic references.
34 
35## Output
36 
37One line per finding, ranked: `<tag> <what to cut>. <replacement>. [path]`.
38End with `net: -<N> lines, -<M> deps possible.` Nothing to cut: `Lean already. Ship.`
39 
40## Boundaries
41 
42Scope: over-engineering and complexity only. Correctness bugs, security holes,
43and performance are explicitly out of scope. Route them to a normal review
44pass. Lists findings, applies nothing. One-shot.
45"stop ponytail-audit" or "normal mode" to revert.
46 

Discussion