ponytail-audit

Audits an entire codebase for over-engineering and ranks findings to delete or simplify.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lrstanley/skills --skill ponytail-audit-lrstanley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/lrstanley/skills/tree/main/ponytail-audit
Command: npx skills add https://github.com/lrstanley/skills --skill ponytail-audit-lrstanley

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/native equivalents. ## Core Features & Use Cases - Whole-Repo Scan: Unlike a diff-based review, it audits the entire tree for bloat, dead flags, unused config, and single-implementation abstractions. - Tagged Findings: Each finding is labeled delete, stdlib, native, yagni, or shrink, with a concrete replacement named. - Ranked One-Shot Report: Outputs one line per finding ordered biggest cut first, ending with a net line/dependency savings estimate. - Use Case: Before a major refactor, run the audit to identify wrappers that only delegate, factories with one product, and dependencies the platform already provides, then hand the list to your team for cleanup. ## Quick Start Ask the AI to run ponytail-audit on this repository 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 ponytail-audit against the repository root. It scans the whole tree and returns a ranked list of findings tagged delete, stdlib, native, yagni, or shrink, each with a concrete replacement suggestion and file path.

How to find dead code and unused dependencies in a repo?▼

The audit hunts for dead flags, unused config, wrappers that only delegate, and dependencies duplicating platform or standard library features. Findings are ranked biggest cut first with an estimated net line and dependency reduction.

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

ponytail-review analyzes a single diff, while ponytail-audit scans the entire codebase. Both use the same tagging system, but the audit produces a one-shot whole-repo report instead of reviewing incremental changes.

Does the audit automatically fix or delete the code it finds?▼

No. It only lists findings and applies nothing. The report is one-shot, and you decide which recommendations to implement manually or in a separate change pass.

What issues are out of scope for an over-engineering audit?▼

Correctness bugs, security vulnerabilities, and performance problems are explicitly out of scope. Those should be routed to a normal code review pass; the audit covers only complexity and bloat.