skills.rest
Reimonsk8
Reimonsk8COMMUNITY
Explore all skills by this author →
Website𝕏@reimonsk8GitHub

ponytail-review

Review diffs for over-engineering and list deletable code with one-line findings.

Updated May 29, 2026
Search Tags:#code quality#code review#refactoring#diff#yagni#simplification#over-engineering
One-click install
npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-review-reimonsk8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/Reimonsk8/hermes-9router-model-balancing/tree/main/plugins/ponytail/.openclaw/skills/ponytail-review
Command: npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-review-reimonsk8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss the simplest improvement: deleting unnecessary code. This Skill reviews a diff specifically for over-engineering, identifying reinvented standard library functions, needless dependencies, and speculative abstractions so the diff can get shorter instead of longer. ## Core Features & Use Cases - Over-Engineering Detection: Finds dead code, hand-rolled utilities the standard library already ships, and dependencies that duplicate native platform features. - Tagged One-Line Findings: Each finding uses a strict format with tags like delete:, stdlib:, native:, yagni:, and shrink:, naming the exact replacement. - Net-Line Scoring: Ends every review with a net: -<N> lines possible. metric, or reports Lean already. Ship. when nothing can be cut. - Use Case: Paste a pull request diff that adds a 27-line email validator class, and receive a finding like L12-38: stdlib: 27-line validator class. "@" in email, 1 line, real validation is the confirmation mail. ## Quick Start Ask the AI to review the current diff with ponytail-review and list everything that can be deleted or replaced with standard library equivalents.

Frequently Asked Questions about ponytail-review

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

FAQPage Schema
How do I review a diff for over-engineering?▼

Run ponytail-review on the diff and it returns one line per finding with a tag, what to cut, and the replacement. It ends with a net-lines-removed score so you can see how much shorter the diff can get.

What kinds of issues does an over-engineering code review find?▼

It finds five categories: dead code to delete, hand-rolled logic the standard library ships, dependencies duplicating native platform features, speculative abstractions with one implementation, and verbose logic expressible in fewer lines.

Does ponytail-review catch bugs or security issues?▼

No, it only flags complexity. Correctness bugs, security holes, and performance problems belong to a normal review pass, which this Skill explicitly excludes from its scope.

Does the review apply the suggested code deletions automatically?▼

No, it only lists findings with locations and replacements. The developer decides which suggestions to apply, keeping the review advisory rather than destructive.

When should I not use an over-engineering review?▼

Skip it when the diff needs 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 it treats as the minimum, not bloat.

Related Skills

Explore More Software Engineering Skills→
arbiterForgearbiterForge
139

commit-gate

Enforce a nine-phase commit workflow with tests, linting, and secrets scanning.

Official
Advanced
Probably-GroupProbably-Group
3

test-runner

Automatically rerun relevant tests on file changes across JavaScript, TypeScript, Python, Rust, and Go.

Official
Intermediate
RightNow-AIRightNow-AI
18.1k

code-reviewer

Analyze source code for bugs, security vulnerabilities, and performance regressions.

Official
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate