Files
ponytail/skills/ponytail-audit/SKILL.md
T
Arthur MorrillandClaude Opus 4.8 b0c5820bb1 Fix scope ambiguity in ponytail-audit and ponytail-review Boundaries (#163)
The Boundaries line opened with "Complexity only, correctness bugs, security
holes, and performance go to a normal review pass." The comma after "Complexity
only" fuses the in-scope item with the out-of-scope list, so a model parsing it
literally can read all four categories as targets of the audit — the opposite of
intent.

Restate the boundary as an explicit scope fence: name what is in scope, then
mark correctness/security/performance as explicitly out of scope. "Out of scope"
is phrasing models reliably honor as a constraint. Also aligns the scope term
with each skill's stated purpose (over-engineering).

Applied to both skills/ and the .openclaw/ mirror so the two trees stay in sync.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-19 00:26:33 +02:00

42 lines
1.6 KiB
Markdown

---
name: ponytail-audit
description: >
Whole-repo audit for over-engineering. Like ponytail-review, but scans the
entire codebase instead of a diff: a ranked list of what to delete, simplify,
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.
---
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.
- `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.
## 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.