Supported path (Tier-1)

One sentence

Block risky AI-assisted merges on Next.js (App Router) repos using GitHub pull requests and a CI job that runs shipgate next — recommended as an advisory gate first; in your repo you may promote it to a required status check once behavior is trusted. Tier‑1 does not require a ShipGate cloud account or dashboard; optional telemetry is off by default (data handling).

Under 30 seconds

1. Install — npm install -g @shipgate.dev/cli@3.0.0 (see package identity; binary is still shipgate)
2. Add CI on pull requests — Prefer the shipgate-next composite (see examples/golden-path-next) or follow CI/CD integration.
3. Enforcement — After validation, optionally mark the job as a required status check so NO_SHIP fails CI and blocks merge. In the ShipGate monorepo, CI runs two required shipgate next --strict jobs (CLI fixture + flagship dashboard) under CI Gate; shipgate-pr-gate uses the same two roots with blocking parity and PR comments — not every Next app in the workspace is enforced yet. Truth map: docs/dogfooding-status.md.
4. Fix — Use CLI output and the Markdown summary (blockers and warnings) to remediate.
5. Export — Use --evidence-out and --summary-out for JSON + Markdown artifacts (schemas ship in the @shipgate.dev/cli package).

Specifications & advanced flows

ISL (.isl files), shipgate gate, shipgate verify, codegen, and shipgate go are spec-driven or best-effort paths. They are real parts of the monorepo but not the Tier‑1 commercial wedge. Use them when you intentionally adopt specifications — not as the first message to a new buyer.

Full matrix & positioning rules

• Coverage and “supported vs best-effort”: docs/supported-matrix.md in the ShipGate repository.
• Product-surface rules (what we say in README, CLI, Actions): docs/product-surface-decision.md.

Also see Tier-1 supported surface and exit codes on this site.