Skip to main content
Nothing is “done” without a check you can run — a test, a build exit code, a screenshot. Forge’s verification gates each add one more catch. With per-task miss rate 1 − p and a gate catch rate c, silent misses fall to (1 − p)(1 − c), and every gate here is one more c.
Verification reduces, does not certify. Crew verifiers and the hallucinated-symbol flag cut review burden; they do not prove the code correct. Tests and human corrections always win.

Independent verification — forge verify

An independent gate: it runs the repo’s real tests, flags hallucinated symbols, and checks provenance.
--deep (v0.19+) escalates to a multi-lens consensus: the change must clear several independent verification lenses, not just one.

The hallucinated-symbol flag — forge atlas has

forge atlas has <symbol> is the hallucination check: if the model calls a symbol that is not in the code graph, the gate flags it.
The atlas is plain JSON on purpose — Codex, Cursor, Gemini, and Aider read .forge/atlas.json via the CLI or plain jq, with no MCP dependency to consume.

Spec-as-contract — forge spec

Pin behavior to a spec and detect drift from it:

The skill-gate — forge scan

Before installing a skill or MCP server, vet it for injection, RCE, or exfiltration:
A clean scan is not a safety certification. The built-in heuristic only catches known attack shapes (critical) and a few high-severity patterns; a pass means “no critical signature detected”, not “safe to install”. Always review the source, permissions, package provenance, and network behaviour yourself. A high-severity finding is not marked safe even though it does not hard-block. The external scanner is opt-in and runs no network call unless you enable it.

Hardening — forge harden

Wire the security controls that keep secrets and unsafe changes out:

Commit-level gate — forge precommit

forge precommit (v0.19+) is a commit-level gate — it runs the verification floor at commit time so partial or unverified work is caught before it lands.

UI checks — forge uicheck

Deterministic UI checks, no LLM and no screenshots for the first three lenses:
Pair it with forge taste to pick one visual direction (brutalist, corporate, editorial, minimalist, playful) and parameterize the design gate thresholds.