ponytail-review

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-review-rasslonely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/Rasslonely/NexusXRP/tree/main/.agents/skills/ponytail-review
Command: npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-review-rasslonely

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 line-reduction 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 dropped for Intl.DateTimeFormat. ## 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 this review on a diff and it flags unnecessary complexity with one line per finding: location, what to cut, and what replaces it. It ends with a net line count showing how much shorter the code could be.

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

It finds five categories: dead code (delete), hand-rolled standard library functionality (stdlib), dependencies duplicating platform features (native), speculative abstractions with one implementation (yagni), and logic expressible in fewer lines (shrink).

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.

When should I not use an over-engineering review?

Avoid it when you need correctness verification, security auditing, 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.

Does 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.