check-vercel-rules

Run the Vercel Labs agent-skills rule checker across a broader scope than the automatic per-edit hook — the whole project, a set of changed files, or as a CI gate.

Usage

Claude: /rn-dev-agent:check-vercel-rules [options]
Codex:  $rn-dev-agent:check-vercel-rules [options]

Modes

Argument	Behavior
(none)	--all walk of the current project; reports violations; exit 0
--changed [files...]	Check only the specified files (or stdin, one per line)
--all	Walk the project for .tsx/.jsx/.ts/.js files (max 200)
--ci	Same as --all but exits 1 on any violation — for pre-commit/CI
--baseline-snapshot	Snapshot current violations as a baseline; later runs report only new ones
--format hook|json|sarif	Output shape (default hook); SARIF 2.1.0 uploads cleanly to GitHub code scanning

One checker, three call sites

The same underlying checker runs in three places:

1. Claude PostToolUse hook — automatic and per edited file; Codex does not consume it.
2. This host workflow — manual, project- or changed-files-scoped.
3. CI / pre-ship gating — --ci blocks on violations.

The checker and rules index ship inside both host packages, so installed Codex workflows do not depend on an rn-dev-agent source checkout. Each violation cites packaged rule metadata and upstream provenance. Retrofitting an existing codebase? Take a --baseline-snapshot first so only new violations surface.

See also

• Best practices rule index — the full 118-rule corpus the checker draws from