skills.rest
malinskibeniamin
malinskibeniaminCOMMUNITY
Explore all skills by this author →
GitHub

ponytail-review

Identify and prune over-engineered diffs in code reviews.

3|1|Updated Mar 23, 2026
Search Tags:#review#diff#code#over-engineering#simplify#deslop
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill ponytail-review-malinskibeniamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/malinskibeniamin/skills/tree/main/ponytail-review
Command: npx skills add https://github.com/malinskibeniamin/skills --skill ponytail-review-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews and simplifies code changes by identifying over-engineered diffs and proposing removals or replacements.

Core Features & Use Cases

  • Flag over-engineered diffs for simplification.
  • Propose inline deletions, desloping, or stdlib/native replacements.
  • Use Case: during pull request reviews to reduce complexity and improve maintainability.

Quick Start

Run the ponytail-review on the current diff to prune excessive complexity.

Frequently Asked Questions about ponytail-review

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

FAQPage Schema
How do I identify over-engineering in a code review?▼

To identify over-engineering in a code review, analyze the diff to flag redundancy, unnecessary abstraction, and excessive complexity, then propose inline deletions or native stdlib replacements to simplify the changes.

What is desloping a code diff?▼

Desloping a code diff is the process of detecting and pruning over-engineered changes in patch reviews or PR change-sets, replacing complex patterns with simpler, standardized alternatives to improve maintainability.

How do I simplify unnecessary abstractions in pull request diffs?▼

To simplify unnecessary abstractions in pull request diffs, review the change-set to detect redundant layers and apply inline substitutions or native replacements, removing complexity across languages and vendor code.

Does ponytail-review work with vendor code diffs?▼

Yes, ponytail-review works with vendor code diffs. It applies over-engineering detection and simplification guidance to standardized diff formats across various languages, including vendor-provided patch reviews.

When should I not use over-engineering detection on a patch review?▼

You should not use over-engineering detection on patch reviews when the diff introduces necessary complexity for future scalability or strict architectural compliance, as the Skill focuses on pruning redundancy and replacing patterns with simpler alternatives.

Related Skills

Explore More Software Engineering Skills→
shouqitaoshouqitao

lybtzyzs-mvp-compliance

Scan code for disallowed technologies and over-engineered patterns.

Community
Intermediate
meowgorithmmeowgorithm
34

bash

Format and lint bash scripts using shfmt and shellcheck.

Community
Intermediate
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced
browseros-aibrowseros-ai
50

dev5-review

Review code changes for correctness, style, and risks, then generate feedback and a commit.

Official
Advanced