ponytail-review

Reviews code diffs for over-engineering and lists what to delete or simplify.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lrstanley/skills --skill ponytail-review-lrstanley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/lrstanley/skills/tree/main/ponytail-review
Command: npx skills add https://github.com/lrstanley/skills --skill ponytail-review-lrstanley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate unnecessary complexity: reinvented standard library functions, speculative abstractions, unused dependencies, and dead flexibility. This Skill performs a focused review pass that hunts only over-engineering, telling you exactly what to cut and what replaces it. ## Core Features & Use Cases - Complexity-Only Review: Flags dead code, hand-rolled stdlib equivalents, unneeded dependencies, and speculative abstractions using five tags: delete, stdlib, native, yagni, shrink. - One-Line Findings: Each finding is a single line with location, what to cut, and the replacement, ending with a net lines-removable score. - Use Case: After a large feature branch, ask for an over-engineering review to find that a 27-line validator class can be replaced by a one-line check, or that moment.js can be swapped for Intl.DateTimeFormat with zero dependencies. ## Quick Start Ask the AI to review this diff for over-engineering and tell me what can be deleted.

Frequently Asked Questions about ponytail-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code for over-engineering?▼

Invoke the review on a diff and it flags over-engineering with five tags: delete, stdlib, native, yagni, and shrink. Each finding is one line showing the location, what to cut, and what replaces it, ending with a net lines-removable score.

What kinds of complexity does an over-engineering review find?▼

It finds dead code and unused flexibility, hand-rolled logic the standard library already ships, dependencies duplicating native platform features, abstractions with a single implementation, and logic that can be written in fewer lines.

Does this review catch bugs or security issues?▼

No. Correctness bugs, security holes, and performance problems are explicitly out of scope and should be routed to a normal review pass. This review only hunts complexity and over-engineering.

Will the review apply the suggested deletions automatically?▼

No. It only lists findings with locations and replacements; it does not modify the code. You decide which suggestions to apply in a separate editing step.

When should I not use an over-engineering review?▼

Skip it when you need correctness, security, or performance feedback, since those are out of scope. It also never flags a single smoke test or assert-based self-check, which is considered the minimum, not bloat.