| name | ponytail-review |
| description | Review diffs for over-engineering only — delete-list with stdlib/native/yagni tags. Use for "ponytail-review", "review for over-engineering", "what can we delete", "simplify review", or before merge when the diff looks bloated. Complements deslop (AI slop) and code-reviewer (correctness). |
When to use
- "ponytail-review", "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review"
- Before merge when a diff added abstractions, deps, or wrappers without clear need
On-demand loading: Read this file when the task matches the triggers above.
Activation: Over-engineering and complexity only. Correctness, security, and performance are out of scope — route those to code-reviewer, differential-review, or security-review.
Inspired by ponytail-review (MIT); adapted for KS bundle.
Ponytail review (diff)
Review the current diff for unnecessary complexity. One line per finding: location, what to cut, what replaces it. The best outcome is a shorter diff.
Format
path:Lstart-Lend: tag: finding. replacement.
Tags:
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.
Process
- Obtain diff (
git diff main...HEAD or user-provided range).
- Apply tags per finding; do not apply fixes unless explicitly asked.
- End with
net: -N lines possible. or Lean already. Ship. if nothing to cut.
Boundaries
- Does not apply fixes by default — lists only.
- A single smoke test or project-convention test is not bloat; never flag it for deletion.
- Pair with
deslop when AI narration comments are also present.
