Skip to content
rn-dev-agent

Reference

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

Section titled “Usage”
/rn-dev-agent:check-vercel-rules [--all | --changed [files...] | --ci | --baseline-snapshot] [--format hook|json|sarif]

Modes

Section titled “Modes”
ArgumentBehavior
(none)--all walk of the current project; reports violations; exit 0
--changed [files...]Check only the specified files (or stdin, one per line)
--allWalk the project for .tsx/.jsx/.ts/.js files (max 200)
--ciSame as --all but exits 1 on any violation — for pre-commit/CI
--baseline-snapshotSnapshot current violations as a baseline; later runs report only new ones
--format hook|json|sarifOutput shape (default hook); SARIF 2.1.0 uploads cleanly to GitHub code scanning

One checker, three call sites

Section titled “One checker, three call sites”

The same underlying checker runs in three places:

  1. PostToolUse hook — automatic, per edited file, during agent sessions.
  2. This command — manual, project- or changed-files-scoped.
  3. CI / pre-ship gating — --ci blocks on violations.

Each reported violation cites a rule ID and points at the upstream rule file for the explanation and fix. Retrofitting an existing codebase? Take a --baseline-snapshot first so only new violations surface.

See also

Section titled “See also”