ponytail-review

Analyze git diffs to identify deletable bloat and over-engineered patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bketelsen/ytsejam --skill ponytail-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-review
Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/ponytail-review
Command: npx skills add https://github.com/bketelsen/ytsejam --skill ponytail-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers detect and reduce unnecessary complexity in diffs by pinpointing deletable bloat and over-engineered patterns, producing concise, actionable findings.

Core Features & Use Cases

  • Step through diffs and locate bloated patterns that can be removed.
  • Apply the ladder lens (delete, stdlib, native, dep, yagni) to prioritize changes.
  • Integrate with code reviews and subagents to scale for large diffs and complex changes.
  • Complement correctness-focused reviews by focusing on maintainability and simplicity.

Quick Start

Review the latest diff with ponytail-review to surface deletable bloat and one-line-per-finding recommendations.

Frequently Asked Questions about ponytail-review

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

FAQPage Schema
How do I detect over-engineering and code bloat in a pull request diff?

To detect over-engineering in a pull request diff, analyze the changes for deletable bloat and unnecessary complexity. The review process applies a ladder lens to pinpoint bloated patterns, producing concise, actionable findings formatted with tags like delete:, stdlib:, native:, dep:, and yagni!.

What is the ladder lens used for in code review workflows?

The ladder lens in code review workflows is used to prioritize changes by applying a hierarchy of tags: delete, stdlib, native, dep, and yagni. It helps engineers evaluate whether code can be removed, replaced with standard libraries, or eliminated as unnecessary complexity.

Can I use this approach to review large git diffs and patch sets?

Yes, you can review large git diffs and patch sets by integrating the analysis with subagents. This scaling approach handles complex changes and large diffs by breaking down the review process to surface deletable bloat and one-line-per-finding recommendations.

Does this code review method check for correctness or maintainability?

This code review method focuses on maintainability and simplicity rather than correctness. It complements correctness-focused reviews by specifically targeting unnecessary complexity and deletable bloat, ensuring the diff remains concise and maintainable.

What do the delete, stdlib, and yagni tags mean in diff analysis?

In diff analysis, tags like delete, stdlib, native, dep, and yagni indicate specific reduction strategies. Delete marks removable code, stdlib suggests using standard libraries, native implies native alternatives, dep targets dependencies, and yagni flags unnecessary speculative features.