ponytail-audit

Audits an entire codebase for over-engineering and ranks deletable code, dependencies, and abstractions.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-audit-rasslonely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/Rasslonely/NexusXRP/tree/main/.agents/skills/ponytail-audit
Command: npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-audit-rasslonely

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 for dead code, unused flexibility, and speculative features. - Tagged Findings: Each finding is labeled as delete, stdlib, native, yagni, or shrink, with a concrete replacement named for each. - Ranked One-Shot Report: Outputs one line per finding ordered biggest cut first, ending with a net estimate of removable lines and dependencies. - Use Case: Before a major refactor, run the audit to discover that a custom retry wrapper duplicates a platform feature and three single-implementation interfaces can be collapsed, cutting hundreds of lines. ## 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.

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

Hunt for dead flags and config nobody sets, files exporting one thing, wrappers that only delegate, and dependencies duplicating what the standard library or platform already ships. The audit reports each with its file path and a net line and dependency reduction estimate.

What is the difference between a repo-wide audit and a diff code review?

A diff review examines only changed lines in a pull request, while a repo-wide audit scans the entire codebase for accumulated bloat. Use the audit for periodic cleanup and the diff review for ongoing change validation.

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

No, it is a one-shot report that only lists findings and applies nothing. You review the ranked list and decide what to remove, then run it again after cleanup if needed.

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

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