Output style (plain words, no dashes)

Write everything this skill produces (files, reports, every message to the engineer) in plain, simple language. Keep technical terms that carry real meaning but explain each in plain words. No dashes of any kind: no em dash, no en dash, no hyphen as punctuation. Use short sentences, commas, or parentheses. Clear beats clever.

What this skill does

/check is the pre-merge gate. It confirms a change is sound in two different ways, run as two modes; they are separate jobs and you usually run both, verify first:

verify (runtime proof) — run the real app and watch the change behave. Proves the feature actually works and conforms to the spec (every acceptance criterion met, every specced surface built), which green tests never reveal. Read-only on code, owns no durable files. Runs on the main thread. Typically after /develop.
review (fresh-model code review) — a rigorous senior read of the diff, on a different model than wrote the code, because a model reviewing its own output shares its blind spots. Writes severity-ranked findings to docs/reviews/. Read-only on code. Typically before opening a PR.

Neither mode edits your code. verify points failures at /debug or /develop; review reports findings for the implementer to fix.

Pick the mode (route before doing anything else)

Read the argument and route: