Verified:GitHub

ponytail-review

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

Updated Sep 10, 2026

Search Tags:#diff analysis #code review #refactoring #yagni #dead code #simplification #over-engineering

One-click install

npx skills add https://github.com/longqt321/Rendez --skill ponytail-review-longqt321

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/longqt321/Rendez/tree/main/.agent/skills/ponytail-review
Command: npx skills add https://github.com/longqt321/Rendez --skill ponytail-review-longqt321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate unnecessary complexity: reinvented standard library functions, unused dependencies, speculative abstractions, and dead flexibility. This Skill reviews diffs exclusively for over-engineering and tells you exactly what to cut, one line per finding. ## Core Features & Use Cases - Complexity-Only Review: Hunts dead code, hand-rolled stdlib replacements, unneeded dependencies, and speculative abstractions while explicitly ignoring correctness, security, and performance issues. - Tagged One-Line Findings: Each finding uses a tag (delete, stdlib, native, yagni, shrink) with the location, what to cut, and what replaces it. - Net-Line Scoring: Ends every review with a single metric estimating how many lines the diff could lose. - Use Case: Before merging a pull request, run this review to discover that a 27-line validator class can be replaced by a one-line check, or that a moment.js import 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 or simplified.

Frequently Asked Questions about ponytail-review

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

FAQPage Schema

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 is also not useful for diffs that are already minimal, in which case it simply reports the code is lean.