ponytail-audit

To audit your codebase for over-engineering, run the ponytail-audit skill on your repository. It scans the entire codebase to identify dead code, unnecessary complexity, and dependencies that could be replaced by standard library functions.

The best way to identify technical debt from unnecessary complexity is to perform a code audit using a tool that ranks over-engineered elements. This provides actionable insights on what code to delete, simplify, or replace with standard library equivalents.

Yes, you can use this code audit tool to find dependencies that standard libraries already cover. It specifically scans for dependencies on standard library functions to guide you on what to replace during code optimization.

You need a code audit for codebase bloat when you want to optimize performance and maintainability or reduce technical debt. It is highly effective for identifying over-engineered parts during a one-time repository review.

Yes, dependency analysis works for any codebase looking to optimize performance and maintainability. It scans the entire codebase to detect over-engineering and provides a ranked list of elements for optimization.