ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.
Install
git clone https://github.com/DietrichGebert/ponytail /tmp/ponytail && ln -s /tmp/ponytail/skills/ponytail-review ~/.claude/skills/ponytail-reviewFrom README
Understand first Review what the user names: uncommitted or staged changes, a branch, a PR link, or files. Nothing named: the uncommitted changes, or the last commit if there are none. Read the diff, then the code it touches: callers of every changed function, the functions it calls, the tests, the README. Trace the real flow: where data comes in, what is stored, what goes out. A change can break code it does not touch. When a signature, return value or behavior changes, grep every caller. Find the expected load in the repo (README, deploy config): one person running a script, or many users and processes at once. Judge scale against that, and say which load you assumed. Look for Bug: wrong result, crash, missed edge case (empty, zero, last item, rounding, time zones), a caller broken by the change, a fix applied in one caller while the shared function stays broken.