skills.rest
Sambhav242005
Sambhav242005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ponytail-audit

Audits an entire codebase for over-engineering and produces a ranked list of deletions and simplifications.

Updated Aug 7, 2026
Search Tags:#code review#refactoring#code audit#tech debt#dead code#simplification#over-engineering
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-audit-sambhav242005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/ponytail-audit
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-audit-sambhav242005

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 reports exactly what to delete, simplify, or replace, ranked by impact. ## Core Features & Use Cases - Whole-Repo Over-Engineering Scan: Hunts for dead code, single-implementation interfaces, one-product factories, delegating wrappers, unused config flags, and hand-rolled stdlib equivalents. - Tagged Findings: Classifies each finding 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 refactor sprint, ask for an audit of your repo to identify which dependencies can be dropped in favor of platform-native features and which abstraction layers have only one caller. ## Quick Start Ask the assistant 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 every file for dead code, single-implementation abstractions, and redundant dependencies. The output is a ranked list of findings tagged by type, with the biggest cuts listed first.

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

Scan for files exporting one thing, interfaces with a single implementation, factories with one product, wrappers that only delegate, and config flags nobody sets. Each finding is tagged so you know whether to delete it or replace it.

What kinds of findings does a code bloat audit report?▼

Findings are tagged as delete (dead code), stdlib (hand-rolled standard library equivalents), native (platform already provides it), yagni (speculative abstraction), or shrink (same logic in fewer lines). Each includes a concrete replacement suggestion.

Does the audit automatically fix or refactor the code?▼

No, it is a one-shot report that only lists findings and applies nothing. You review the ranked list and decide which deletions or replacements to make yourself.

What 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 code review pass instead.

Related Skills

Explore More Software Engineering Skills→
TairitsuaTairitsua
13

third-party-source-catalog

Catalog and fetch third-party library source trees from GitHub repositories and local folders.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

refactoring

Refactor code incrementally with tests and isolated commits.

Official
Advanced
kaminocorpkaminocorp
1

Scope Assessment

Verifies a target repository is in-scope for its bug bounty program before analysis.

Official
Intermediate
MWest2020MWest2020

ponytail-audit

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

Community
Basic