vienen-las-visitas

¡Vienen las visitas!

Someone who was not here is about to read this. Read it first, the way they will.

Rule

This is the last gate before the boundary, and it runs once per crossing — not once per commit. It composes rather than duplicates: cleanup belongs to recoge-tu-tiradero, success evidence belongs to a-ver-ensename, and this skill invokes them instead of restating them. What it owns is the crossing itself — the diff, the message, and the reviewer.

Closure order: pero-tu-primo → recoge-tu-tiradero → a-ver-ensename → this skill. Compare first, then clean, then prove, then hand off. Arriving here with the earlier three unrun means you are not at this gate yet.

Honesty outranks tidiness. Hiding a known limitation so the diff looks clean is the exact opposite of this skill. Mom cleans the house; she does not lie about what is in the closet. State known gaps plainly, up front, in your own words — before the reviewer finds them.

Procedure

Run the delegated steps first, then the seven this skill owns.

1. Read your own diff, top to bottom, as the reviewer would. Whole thing, every hunk, in order — not the summary, not the file list. This catches more than any tool on this list, and skipping it invalidates the rest.
2. Every file in the diff is one you meant to touch. Hunt specifically for what you did not intend: formatter reflows across untouched files, lockfile churn from an incidental install, editor and IDE config, .DS_Store, scratch files, whitespace-only noise. Anything you cannot explain, revert.
3. No secrets. Tokens, API keys, real credentials, connection strings, private endpoints and internal URLs, customer or personal data — including in fixtures, test files, comments, example configs, and committed output. This is the last moment for a secret scan.
4. No debug residue left switched on. .only and .skip, commented-out assertions, verbose or trace-level logging, feature flags flipped for local testing, a timeout raised to make something pass, a mock left standing in for the real call.
5. The message describes the change honestly. The PR or commit message says what the change does and what it does not do. No claim beyond what a-ver-ensename proved. Scope stated in the same words the diff would use.
6. The reviewer has what they need. Why, not just what — the problem being solved. A test plan they can run themselves. Known limitations stated up front rather than discovered. If they would have to ask you a question to review it, answer it now.
7. Anything intentionally left undone is named. Deferred work goes in the message by name, not in your head — see no-se-te-olvide-que for tracking it and ahorita for the deferral itself. "I'll clean that up later" that nobody else can see is not deferred; it is hidden.