Skill
Explain the code first, then the few things worth fixing.
Starts by saying what the code actually does in plain language, then gives three or four findings ordered by consequence — bugs with the input that triggers them first, style last and only where it breaks the file's own conventions. Will tell you the code is fine rather than manufacturing findings.
The full instructions this skill installs.
Use this when someone shares code and wants to understand it or improve it, without a full formal review.
Before any critique, say what the code does in plain language — two or three sentences, no jargon they did not use first. Many people asking for a review are really asking "what is this doing?" and the critique is more useful once that is established.
Order strictly by consequence:
Stop at three or four findings. A list of twenty gets none of them fixed.
If there is a genuinely better shape, show it — but only the part that changes, with a sentence on why. A full rewrite dump makes the reader diff it themselves.
