P

ponytail-review

by @dietrichgebertv
4.7(120)

This skill specializes in reviewing code diffs to identify over-engineering, unnecessary complexity, and redundant code. It focuses on finding content to delete, such as reinvented standard library functions, needless dependencies, and speculative abstractions. By doing so, it helps developers write leaner, more maintainable code, improving overall code quality and reducing technical debt.

code-reviewrefactoringcode-qualityover-engineeringsimplificationGitHub
Installation
npx skills add https://github.com/dietrichgebert/ponytail --skill ponytail-review
compare_arrows

Before / After Comparison

1 组
Before

When manually reviewing code, developers often overlook over-engineered and redundant code due to oversight or lack of experience, leading to bloated codebases, increased maintenance costs, and significant time consumption.

After

This Skill can quickly and accurately identify over-engineered parts of the code and provide specific deletion or replacement suggestions, significantly improving the efficiency and quality of code reviews, and effectively reducing technical debt.

SKILL.md

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.

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs55.4K
Rating4.7 / 5.0
Version
Updated2026年10月24日
Comparisons1

User Rating

4.7(120)
5
37%
4
43%
3
13%
2
5%
1
2%

Rate this Skill

0.0

Compatible Platforms

🤖claude-code

Timeline

Created2026年6月25日
Last Updated2026年10月24日
🎁 Agent Knowledge Cards
Survey