ponytail-audit

Audits an entire codebase for over-engineering and ranks findings by deletion impact.

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

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, so you can cut bloat without a manual line-by-line review. ## Core Features & Use Cases - Whole-repo over-engineering scan: Unlike a diff-based review, it audits the entire tree for dead code, unused flexibility, and speculative features. - Tagged findings: Each finding is labeled delete, stdlib, native, yagni, or shrink, with a concrete replacement named (e.g., the stdlib function or platform feature to use instead). - Ranked one-shot report: Outputs one line per finding ordered biggest cut first, ending with a net estimate of removable lines and dependencies. It lists findings only and applies no fixes. - Use Case: Before a major refactor, run the audit to identify single-implementation interfaces, one-product factories, wrapper-only modules, and dead config flags, then hand the ranked list to your team as a cleanup backlog. ## Quick Start Ask the AI to audit this codebase for over-engineering and list what can be deleted or replaced with standard library equivalents.

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 codebase for over-engineering?

Run a whole-repo audit that scans every file for dead code, speculative abstractions, and stdlib duplicates, then ranks findings biggest cut first. Each finding is tagged delete, stdlib, native, yagni, or shrink with a concrete replacement.

How to find dead code and unused abstractions in a repository?

Look for single-implementation interfaces, factories with one product, wrappers that only delegate, files exporting one thing, and dead flags or config. The audit hunts exactly these patterns across the whole tree and reports them as one-line findings.

What is the difference between a repo-wide audit and a diff review?

A diff review examines only changed lines in a pull request, while a repo-wide audit scans the entire codebase. Use the audit for accumulated bloat and legacy cleanup; use diff review for catching issues in new changes.

Does the over-engineering audit also find bugs or security issues?

No. The audit scope is strictly over-engineering and complexity. Correctness bugs, security holes, and performance problems are explicitly out of scope and should be routed to a normal review pass.

Will the audit automatically refactor or delete my code?

No. It is a one-shot report that only lists findings with suggested replacements. It applies nothing, so you review the ranked list and decide what to cut yourself.