ponytail-audit

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

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

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 reading every file yourself. ## 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 removable lines and dependencies, e.g. net: -400 lines, -3 deps possible. - Use Case: Before a major refactor, ask for an audit to find single-implementation interfaces, dead config flags, and wrappers that only delegate, then plan the cleanup sprint. ## Quick Start Ask the AI to audit this codebase for over-engineering and list what can be deleted or replaced with stdlib 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, single-implementation abstractions, and hand-rolled utilities duplicating the standard library. Findings are ranked biggest cut first with a concrete replacement named for each.

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 the platform or stdlib already covers. Each finding is tagged and ends with a net estimate of removable lines and dependencies.

What is the difference between a code review and a codebase audit?▼

A review examines a diff or pull request, while this audit scans the entire repository tree. It focuses only on over-engineering and complexity, producing a one-shot ranked report rather than inline comments on changes.

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

No. It is a one-shot report that lists findings and applies nothing. You review the ranked list and decide what to remove, then run a separate change or review pass to implement the cuts.

What kinds of 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 review pass; the audit only targets complexity, bloat, and unnecessary abstraction.