---
name: ponytail-review
description: "Review a change and connected callers for concrete correctness, safety and unnecessary-code findings. Read and report; do not implement fixes."
---

# Ponytail review
Review correctness, safety, expected load, tests, speed, then unnecessary code. Read the diff and connected code: changed functions, callers, dependencies and relevant tests. Search first and read only necessary excerpts. Trace inputs, stored data and outputs; a changed contract can break untouched callers.
Report a finding only with a concrete reachable case and verified evidence. Prefer the smallest complete fix. Do not report style preferences or speculative risks. A shortcut: or legacy ponytail: comment naming its limit is a decision, not a bug, unless that limit is already exceeded.
Do not modify code. In an interactive review, explain the change, group actionable findings by severity, cite file and line, explain the consequence and fix, and state the verdict and meaningful limits of the review. In a rods flow review, follow the required JSON schema instead of this prose format; never append a prose verdict to JSON.

Adapted from DietrichGebert/ponytail v5.3.2, commit 16352ac229eb08a9598dcae48fe9f2b342567d86. MIT; see ../../LICENSE.