CtrlK
BlogDocsLog inGet started
Tessl Logo

ponytail-audit

Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.

53

Quality

60%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.openclaw/skills/ponytail-audit/SKILL.md
SKILL.md
Quality
Evals
Security

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.

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.

Repository
DietrichGebert/ponytail
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.