agentleFS
Sign inStart free
maxatworkmaxatwork/skills/skills/ponytail-review/SKILL.md

ponytail-review

Skill0 starsChanged 8 days agoMITView on GitHub

Use when changes are ready, such as before committing, opening a PR, or reporting work as done, even if no one asked for a review. Reports unnecessary abstractions, dependencies, or duplication that can be cut without changing behavior; makes no edits.

72 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use caveman-explore, migration and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JuliusBrusseeSkill

    caveman-explore

    Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.

    Also in 4 projects that use this

  • ryu111Skill

    migration

    Migration planning expertise. Use when replacing tools/frameworks, upgrading versions, migrating databases, or planning transitions. Contains strategies, compatibility analysis methods, and rollback planning.

    Also in 5 projects that use this

  • JuliusBrusseeSkill

    surgical-patch

    Fix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant tests matter.

    Also in 3 projects that use this

  • huangzidaSkill

    caveman-help

    Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

    Also in 6 projects that use this

  • huangzidaSkill

    caveman-compress

    Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

    Also in 5 projects that use this

  • jaydubya818Skill

    thermo-nuclear-code-quality-review

    Use when the user requests an intentionally strict maintainability review.

    Also in 5 projects that use this

  • +2 more from JuliusBrussee
  • +2 more from huangzida

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 69 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat shorter validation or retry code as equivalent only after checking its actual acceptance and failure behavior.

    line 18
  2. Distinctive:

    Keep this review scoped to complexity.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 69 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ponytail review

Review the ready changes, or the diff the user names, for unnecessary complexity. Recommend a cut only when the replacement preserves behavior and contracts and reduces maintenance or caller burden. A single caller or implementation is not proof that an abstraction is unnecessary.

Report each finding with a file and line, what changes, why the responsibility no longer needs that code, and the replacement. Useful tags are delete, stdlib, native, yagni, and shrink.

Examples of justified findings:

  • An unused internal flag has no callers or dynamic consumers; remove its branch and configuration.
  • A date library is used only for a format that the target platforms' Intl.DateTimeFormat supports with the same locale behavior.
  • Two wrappers forward the same arguments without owning validation, lifecycle, compatibility, or other policy; remove the redundant layer.

Treat shorter validation or retry code as equivalent only after checking its actual acceptance and failure behavior. Idempotence alone does not remove the need to retry a transient failure.

Keep this review scoped to complexity. Distinguish incidental correctness concerns from the requested findings; do not silently start another audit. Apply no edits unless separately requested. Preserve meaningful checks and established test infrastructure.

Estimate removals only when useful, and label the estimate. With no findings, say no unnecessary complexity was identified in the reviewed scope. This review does not establish readiness to ship.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free