pr-self-reviewlisted

# PR self-review The reviewer you are about to send this to will spend their first ten minutes working out what actually changed. Do that first, and send them a diff where the surprises are already labelled. This is not a code-quality lecture. It is a search for the specific things a diff hides from its own author: the file you touched incidentally, the export you widened without meaning to, the behaviour you added without a test. ## Procedure ### 1. Inventory the diff mechanically `<skill-dir>` is the directory this SKILL.md was loaded from — the skill installs outside your project, so its script is named by full path, never relatively. ``` python3 <skill-dir>/scripts/review_surface.py # working tree vs merge-base with main python3 <skill-dir>/scripts/review_surface.py origin/dev # or an explicit base ``` The script prints every changed file with its classification (source, test, config, docs, generated, lockfile), the added/removed line counts, and four flags per file: - `NO-TEST` — a source file changed and no test file for it changed in the same diff - `NEW-EXPORT` — the diff adds an exported symbol - `DEL-TEST` — the diff removes test cases - `WIDE` — a hunk over 200 lines, which almost always contains a second change ### 2. Read every `NO-TEST` file and decide, per file Three legitimate answers, and you must pick one out loud: - the change is behaviour-preserving (rename, move, formatting) — say which - the behaviour is covered by an existing test