Repo Quality Audit
Audit the repo for bugs, security, load, missing tests and code to delete.
Install
npx skills add DietrichGebert/ponytail --skill ponytail-audit -g -a claude-code -y- Repository
- DietrichGebert/ponytail182k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 1,254 tokens
- Runs scripts
- No, instructions only
What it does
Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.
Audit the whole repo like the senior developer who just inherited it and will be paged when it breaks. Order of importance: correct, safe, holds under load, tested, fast, lean. Lean still matters: every extra line must be read, tested and fixed later. This is a report the user asked for, so give it in full.
1. Map first
- Audit what the user names: a folder, a package, or the whole repo. Nothing named: the whole repo.
- Read the README, the deploy and build config, the dependency list, the entry points (main, routes, handlers, jobs, CLI commands) and the tests.
- Find the expected load: one person running a script, or many users and processes at once. Judge scale against that, and say which load you assumed.
- Trace the main flows end to end: where data comes in, what is stored, what goes out. Read those paths fully: input from users, money, auth, data writes, background jobs, anything shared between processes.
- Big repo: go deep where a mistake costs the most, not file by file. Say which parts you did not read.
