agentleFS
elpabloultronelpabloultron/open-legal-chile/.agents/skills/ponytail-audit/SKILL.md

ponytail-audit

Skill5 starsChanged 48 days agoApache-2.0View on GitHub

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.

75 other projects use a version of this, 46 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use caveman-explore, caveman-discover 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

  • JuliusBrusseeSkill

    caveman-discover

    Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

    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-commit

    Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

    Also in 9 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 4 projects that use this

  • MicrosoftSkill

    impeccable

    Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.

    Also in 11 projects that use this

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

The file

Files
SKILL.md

ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank findings biggest cut first.

Tags

Same as ponytail-review:

  • delete: dead code, unused flexibility, speculative feature. Replacement: nothing.
  • stdlib: hand-rolled thing the standard library ships. Name the function.
  • native: dependency or code doing what the platform already does. Name the feature.
  • yagni: abstraction with one implementation, config nobody sets, layer with one caller.
  • shrink: same logic, fewer lines. Show the shorter form.

📎 Citas y formato de entrega

  • Documentos (informe en derecho, análisis, memorándum, escrito, minuta, dossier): se entregan en Word (.docx), no en PDF, para que se puedan modificar; las citas van a pie de página, numeradas, con fuente · identificador · enlace.
  • Conversación: la respuesta va primero y las citas van al final, después del texto.

En los dos casos: si no hay fuente identificable se dice «sin fuente verificable», y un dato que viene de varias fuentes se cita con todas.

Hunt

Deps the stdlib or platform already ships, single-implementation interfaces, factories with one product, wrappers that only delegate, files exporting one thing, dead flags and config, hand-rolled stdlib.

Output

One line per finding, ranked: <tag> <what to cut>. <replacement>. [path]. End with net: -<N> lines, -<M> deps possible. Nothing to cut: Lean already. Ship.

Boundaries

Scope: over-engineering and complexity only. Correctness bugs, security holes, and performance are explicitly out of scope. Route them to a normal review pass. Lists findings, applies nothing. One-shot. "stop ponytail-audit" or "normal mode" to revert.


🎨 Presentación y Lenguaje Claro (Legal Design)

Overlay de docs/legal_design.md para este repositorio (por eso va en español: es el idioma de trabajo de Open Legal Chile). Esta skill es de código, no de derecho: hereda las reglas de presentación, no las jurídicas.

  • Quién lee: quien mantiene el repositorio, que puede no ser experto en este módulo.
  • Lenguaje claro: todo término técnico o sigla va con su equivalencia simple entre paréntesis la primera vez — yagni (no construyas lo que todavía no se necesita).
  • Salida (estructura): una línea por hallazgo, del corte más grande al más chico, cerrando con net: -<N> lines, -<M> deps possible.
  • Citas: si la salida toca materia jurídica, se cita en el Formato de Citación Obligatorio de AGENTS.md §2 ([BCN - Ley N° 21.643, Art. 2]); si es código, archivo y línea.
  • Compuerta: ⚖️ Compuerta de Revisión Jurídica aplica solo si la salida de esta skill termina en un producto jurídico (escrito, memo, comunicación a contraparte). Una skill que simplifica código no produce asesoría jurídica ni la sustituye.

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.