Ponytail review

Skill hsnuhow/how-skills/plugins/ponytail/skills/ponytail-review

個人 Claude Code plugin marketplace：skill 管理指令（skill-list/status/RCM）＋ commands-only 的 ponytail。

Install

npx -y skills add hsnuhow/how-skills --skill ponytail-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

SKILL.md

2.3 KB, as published. Nobody here has run it

Review diffs for unnecessary complexity. One line per finding: location, what to cut, what replaces it. The diff's best outcome is getting shorter.

Format

L<line>: <tag> <what>. <replacement>., or <file>:L<line>: ... for multi-file diffs.

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.

Examples

❌ "This EmailValidator class might be more complex than necessary, have you considered whether all these validation rules are needed at this stage?"

✅ L12-38: stdlib: 27-line validator class. "@" in email, 1 line, real validation is the confirmation mail.

✅ L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps.

✅ repo.py:L88: yagni: AbstractRepository with one implementation. Inline it until a second one exists.

✅ L52-71: delete: retry wrapper around an idempotent local call. Nothing replaces it.

✅ L30-44: shrink: manual loop builds dict. dict(zip(keys, values)), 1 line.

Scoring

End with the only metric that matters: net: -<N> lines possible.

If there is nothing to cut, say Lean already. Ship. and stop.

Boundaries

Scope: over-engineering and complexity only. Correctness bugs, security holes, and performance are explicitly out of scope. Route them to a normal review pass, not this one. A single smoke test or assert-based self-check is the ponytail minimum, not bloat, never flag it for deletion. Does not apply the fixes, only lists them. "stop ponytail-review" or "normal mode": revert to verbose review style.

Gives 0 of the 12 instructions most review quality skills give

Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-06

ask questions one at a timein 82 of 1048, across 54 files
provide a recommended answer for each questionin 73 of 1048, across 45 files
explore the codebase instead of asking answerable questionsin 66 of 1048, across 37 files
resolve dependencies between decisions one-by-onein 42 of 1048, across 15 files
interview the user relentlessly about the planin 39 of 1048, across 12 files
order findings by severityin 29 of 1048
resolve each branch of the decision treein 28 of 1048, across 5 files
run a grilling sessionin 26 of 1048, across 5 files
update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 9 files
propose precise canonical terms for vague languagein 25 of 1048, across 6 files
create documentation files lazilyin 24 of 1048, across 5 files
use the domain-modeling skillin 22 of 1048, across 3 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.