ponytail-review

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-review-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/optimization/ponytail/ponytail-review
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-review-cloudofgeorge

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 for 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 its replacement, ending with a net line-reduction score. - Use Case: After a large feature diff, ask for an over-engineering review and receive findings like "L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps." so the diff gets shorter before merge. ## Quick Start Review this diff for over-engineering and tell me what we can delete.

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 returns one line per finding: location, what to cut, and what replaces it. Findings are tagged as delete, stdlib, native, yagni, or shrink, and the output ends with a net line-reduction score.

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

It finds dead code and unused flexibility (delete), hand-rolled logic the standard library ships (stdlib), dependencies duplicating platform features (native), abstractions with one implementation (yagni), and logic expressible in fewer lines (shrink).

Does this review also catch bugs and security issues?

No. Correctness bugs, security holes, and performance problems are explicitly out of scope and belong to a normal review pass. This review only hunts unnecessary complexity.

Will the review apply the simplifications automatically?

No. It only lists findings with locations and suggested replacements; it does not modify the code. You decide which cuts to apply.

When should I not use an over-engineering review?

Skip it when you need correctness, security, or performance analysis, 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.