skills.rest
Reimonsk8
Reimonsk8COMMUNITY
Explore all skills by this author →
Website𝕏@reimonsk8GitHub

ponytail-audit

Audits an entire repository for over-engineering and ranks deletable or simplifiable code.

Updated May 29, 2026
Search Tags:#code review#refactoring#repository#code audit#dead code#simplification#over-engineering
One-click install
npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-audit-reimonsk8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/Reimonsk8/hermes-9router-model-balancing/tree/main/plugins/ponytail/.openclaw/skills/ponytail-audit
Command: npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-audit-reimonsk8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate dead code, speculative abstractions, and hand-rolled utilities that duplicate the standard library. This Skill scans the whole repository and produces a ranked list of what to delete, simplify, or replace with stdlib or native platform features. ## Core Features & Use Cases - Repo-wide over-engineering audit: Scans the entire tree instead of a diff and ranks findings biggest cut first. - Tagged findings: Classifies each finding as delete:, stdlib:, native:, yagni:, or shrink: with a concrete replacement suggestion. - Net impact summary: Ends with an estimate of lines and dependencies removable, e.g. net: -300 lines, -2 deps possible. - Use Case: Before a major refactor, run the audit to find single-implementation interfaces, factories with one product, dead config flags, and wrappers that only delegate, then cut them in one pass. ## Quick Start Ask the assistant to run ponytail-audit on this repository and list the top over-engineering findings ranked by biggest cut first.

Frequently Asked Questions about ponytail-audit

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

FAQPage Schema
How do I audit a repository for over-engineering?▼

Run the ponytail-audit skill against the whole repository tree. It scans every file, ranks findings biggest cut first, and outputs one line per finding with a tag, what to cut, and its replacement.

What kinds of code smells does a repo-wide simplification audit find?▼

It finds dead code, unused flexibility, hand-rolled utilities the standard library ships, dependencies duplicating native platform features, single-implementation interfaces, factories with one product, delegating wrappers, and dead config flags.

Does the audit apply the suggested code changes automatically?▼

No. The audit only lists findings and applies nothing. It is a one-shot read-only pass; you decide which cuts to make, and a normal review pass handles correctness, security, and performance concerns.

What is the difference between ponytail-audit and ponytail-review?▼

ponytail-audit scans the whole repository tree for over-engineering, while ponytail-review works on a diff. Both use the same tagging scheme: delete, stdlib, native, yagni, and shrink.

When should I not use an over-engineering audit?▼

Do not use it to find correctness bugs, security holes, or performance problems, since those belong to a normal review pass. The audit scope is strictly complexity reduction and dependency elimination.

Related Skills

Explore More Software Engineering Skills→
JerrylalalaJerrylalala
6

patch-approval

Reviews Codex-generated patch diffs in an isolated git clone before applying them to the workspace.

Community
Intermediate
engasnm111engasnm111
166

ponytail-audit

Audits an entire codebase for over-engineering and ranks deletable or simplifiable code.

Community
Basic
Base-AnaliticaBase-Analitica

ponytail-review

Reviews code diffs for over-engineering and lists what to delete or simplify.

Official
Basic
AminAlamAminAlam
26

Static Analysis for Medical Devices

Enforce MISRA C/C++ and CERT C/C++ compliance in medical device software.

Community
Intermediate