ponytail-audit

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

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill ponytail-audit-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/CHENHUI-X/toolbox/tree/main/codex-skill/codex/ponytail-audit
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill ponytail-audit-chenhui-x

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 cut, so you can reduce maintenance burden without guessing where the bloat lives. ## Core Features & Use Cases - Whole-repo over-engineering scan: Unlike a diff-based review, it audits the entire tree and ranks findings biggest cut first. - Tagged findings: Each finding is labeled delete, stdlib, native, yagni, or shrink, with a concrete replacement named. - Net impact summary: Ends with an estimate of lines and dependencies removable, or confirms the repo is already lean. - Use Case: Before a major refactor, run the audit to find single-implementation interfaces, dead config flags, and wrappers that only delegate, then plan deletion work from the ranked report. ## 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 the full tree instead of a diff and ranks findings biggest cut first. Each finding is tagged delete, stdlib, native, yagni, or shrink with a concrete replacement and file path.

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

Look for single-implementation interfaces, factories with one product, wrappers that only delegate, dead config flags, and files exporting one thing. The audit hunts exactly these patterns and lists them ranked by impact.

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

ponytail-audit scans the entire codebase, while ponytail-review examines only a diff. Both use the same tagging system for delete, stdlib, native, yagni, and shrink findings.

Does the over-engineering audit apply fixes automatically?

No, it is a one-shot report that only lists findings and applies nothing. You review the ranked output and decide what to delete or simplify yourself.

What issues are out of scope for a code bloat audit?

Correctness bugs, security holes, and performance problems are explicitly out of scope and should go to a normal review pass. The audit covers only over-engineering and unnecessary complexity.