ponytail-audit

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

166|78|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-audit-engasnm111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/engasnm111/lnwjud/tree/main/.agents/skills/ponytail-audit
Command: npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-audit-engasnm111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate dead code, redundant abstractions, and hand-rolled utilities that duplicate standard library features. This Skill scans the whole repository and produces a ranked list of what to delete, simplify, or replace, 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 reports 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 cleanup 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 entire tree instead of a diff and ranks findings biggest cut first. Each finding is tagged as delete, stdlib, native, yagni, or shrink, with a concrete replacement named for each item.

What kinds of code bloat can a repo audit find?▼

It finds dead code, unused flexibility, speculative features, hand-rolled utilities the standard library already ships, single-implementation interfaces, factories with one product, wrappers that only delegate, and dead flags or config.

Does the audit automatically delete or refactor code?▼

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

Does an over-engineering audit catch bugs or security issues?▼

No. Correctness bugs, security holes, and performance problems are explicitly out of scope. Those should be routed to a normal code review pass instead.

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

A diff review examines only changed code in a pull request, while a whole-repo audit scans the entire codebase. The audit suits periodic cleanup; the diff review suits per-change quality gates.