ponytail

Reviews code for unnecessary complexity and reports deliberate shortcut comments.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill ponytail-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/oxie/prime-agent-skills/tree/main/ponytail
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill ponytail-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate over-engineered abstractions, speculative features, and untracked shortcuts that increase maintenance cost. This Skill provides an on-demand checklist for simplifying implementations, auditing code for unnecessary complexity, and reporting deliberate technical-debt markers without changing requirements or safeguards. ## Core Features & Use Cases - Implementation Ladder: A six-step ordered checklist that prefers confirming the real need, reusing existing helpers, standard library, native platform features, and installed dependencies before writing new code. - Complexity Review and Audit: Read-only inspection of a diff, file set, or project subtree that returns evidence-backed findings labeled delete, reuse, stdlib, native, or simplify, each with behavior-preservation conditions and risk. - Shortcut Debt Report: Scans agreed source scope for ponytail: comment markers and returns one verified row per comment with simplification, ceiling, and revisit trigger fields. - Use Case: After a feature branch grows a hand-rolled caching layer, invoke the skill to review the diff; it may recommend reusing the existing TTLCache helper with per-user isolation checks, citing exact locations and the regression tests to run. ## Quick Start Ask the agent to review the current diff with the ponytail skill and report any unnecessary complexity with suggested simpler replacements.

Frequently Asked Questions about ponytail

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

FAQPage Schema
How do I review code for over-engineering and unnecessary complexity?▼

Invoke the skill in review or audit mode on a specified diff, file set, or subtree. It returns findings with location, observed complexity, proposed replacement, behavior-preservation conditions, and risk, labeled delete, reuse, stdlib, native, or simplify.

How to simplify JavaScript array filter and map pipelines safely?▼

Check callback order, sparse-array holes versus present undefined values, truthiness traps like filter(Boolean), and lazy iterator timing before fusing passes. Test a distinguishing case in the target runtime, since fewer passes are not equivalent behavior.

Does this skill automatically refactor or fix my code?▼

No. Review, audit, and debt-report modes are strictly read-only and never apply fixes. Only the explicit implement path makes changes, and only those the user authorized.

When should I not use this code simplification skill?▼

Do not use it for ordinary coding already covered by standing project rules, general security or correctness audits, prose review, or visual design. It is an on-demand checklist, not an always-on coding mode.

How do I track deliberate technical debt shortcuts in source code?▼

Add a concise ponytail: comment naming the ceiling and revisit trigger when an authorized trade-off leaves a real limit. The debt report mode then finds and tabulates verified markers with path, line, simplification, ceiling, and trigger.