ponytail-audit

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill ponytail-audit-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/ponytail-audit
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill ponytail-audit-base-analitica

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 scan: Unlike a diff-based review, it audits the entire tree for over-engineering patterns. - Tagged findings: Each finding is labeled delete, stdlib, native, yagni, or shrink with a concrete replacement suggestion and file path. - Ranked one-shot report: Findings are ordered biggest cut first, ending with an estimate of net lines and dependencies removable. - Use Case: Before a major refactor, run the audit to find single-implementation interfaces, factories with one product, dead config flags, and wrappers that only delegate, then hand the 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 find dead code and bloat in my repository?▼

Run a whole-repo over-engineering audit that scans the full tree and tags findings as delete, stdlib, native, yagni, or shrink. Each finding includes a concrete replacement suggestion and file path, ranked biggest cut first.

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

ponytail-audit scans the entire codebase, while ponytail-review only examines a diff. Both use the same tagging system for over-engineering findings, but the audit produces a one-shot repo-wide report.

Does the over-engineering audit automatically fix or delete code?▼

No, it only lists findings and applies nothing. The output is a ranked report with an estimate of net lines and dependencies removable, leaving all changes to you.

What kinds of over-engineering does a codebase audit detect?▼

It detects dead code, unused config flags, single-implementation interfaces, factories with one product, wrappers that only delegate, and hand-rolled utilities the standard library or platform already provides.

When should I not use an over-engineering audit?▼

Do not use it for correctness bugs, security holes, or performance problems, as those are explicitly out of scope. Route those concerns to a normal code review pass instead.