/moai gate

A lightweight gate command that quickly validates quality before a commit. It runs lint, format, type checks, and tests in parallel, completing within 30 seconds on most projects.

Info

One-line summary: /moai gate is a “fast checkpoint before committing.” It runs four checks (lint · format · type · test) simultaneously and tells you pass/fail instantly — without a full code review or coverage analysis.

Info

Slash command: Type /moai:gate in Claude Code to run this command directly. Type just /moai to see the full list of available subcommands.

Use it when you want to check “is the current state clean?” before committing. Unlike /moai review (deep 4-perspective review) or the sync pipeline’s full quality check, /moai gate provides only a fast pass/fail verdict.

# Full check
> /moai gate

# Auto-fix lint and format
> /moai gate --fix

# Check staged files only
> /moai gate --staged

# Check a specific file only
> /moai gate --file src/auth/service.go

flowchart TD
    Start["/moai gate run"] --> Detect["Step 1: Language detection
(marker-file priority)"]
    Detect --> Snap["Step 1B: Consume shared snapshot
(reuse if fresh, skip with --fresh)"]
    Snap --> Parallel

    subgraph Parallel["Step 2: Parallel checks"]
        C1["Lint
style · unused imports"]
        C2["Format
format validation"]
        C3["Type
static type analysis"]
        C4["Test
test suite"]
    end

    Parallel --> Report["Step 3: Report results
(PASS/FAIL/WARN table)"]
    Report --> Next["Step 4: Next steps
(on failure: --fix / /moai fix / ignore)"]

It checks marker files in priority order (first match wins) and selects the language-specific toolchain. All 16 supported languages are treated equally — for example, Go runs go vet · golangci-lint · go test -race, while Python runs ruff · mypy · pytest. When no recognized marker is found, language-specific checks are skipped and “unknown language” is reported.

Before running checks, it queries the shared diagnostic snapshot for the current working tree. When a fresh snapshot (key match + within TTL, default 10 minutes) covers the check categories this gate would run, the recorded results are reused instead of re-running, shown in the report as Test | PASS (snapshot). A stale snapshot is never cited as evidence — it is re-run. In --fresh mode this step is skipped entirely.

The four checks run concurrently in the background.

Per-check timeout is 60 seconds; the overall gate timeout is 90 seconds. On timeout it reports a WARNING but does not block. The results of full-scope checks that actually ran (not reused) are recorded in the shared snapshot store under .moai/state/verify/, so downstream consumers (run-phase pre-review gate, sync pre-gate, stop-goal evaluator) can reuse them while the tree is unchanged.

## Quality Gate: PASS
| Check  | Status | Time  |
|--------|--------|-------|
| Lint   | PASS   | 2.1s  |
| Format | PASS   | 0.8s  |
| Type   | PASS   | 3.2s  |
| Test   | PASS   | 12.4s |
Total: 18.5s

When everything passes, a commit-ready message is shown. When it fails without --fix, AskUserQuestion presents the following — auto-fix (re-run --fix, recommended) / /moai fix (deep resolution) / ignore and proceed. Issues remaining after --fix (type errors, test failures) are recommended for manual investigation.

/moai gate is a lightweight checkpoint that only validates and does not modify files (it corrects lint and format only when given --fix). When deeper resolution is needed, move on to /moai fix (one-shot) or /moai loop (iterative); for a comprehensive pre-PR review, use /moai review. --fresh mode is used when /moai loop’s independent final-verification pass calls this gate to obtain self-reference-free evidence.

• /moai fix - one-shot auto-fix
• /moai loop - iterative fix loop
• TRUST 5 quality system