gates

name	gates
description	Gates

Gates

Mechanical pass/fail checks. No judgment, no opinions - compiler, linter, and tests either pass or they don't. Run before code reviews, after fix batches, and before PRs.

Read REFERENCE.md §1 "Why mechanical gates" for rationale.

Input

$ARGUMENTS = optional scope hint (extension for TS-only, dotnet for C#-only). Default: all applicable gates.

Process

Step 1: Detect What Changed

git diff --name-only main...HEAD

Categorize: .cs -> .NET gates; .ts/.js -> TypeScript gates; both -> all. If $ARGUMENTS specifies a scope, use that.

Step 1.5: Preflight Toolchain & Output Discipline

Before running any gate, confirm its toolchain is on PATH. A missing toolchain is a FAIL, never a SKIP - never report a TS gate as PASS or SKIP when npm is missing.

command -v dotnet >/dev/null 2>&1 || { echo "FAIL (preflight): dotnet missing"; exit 1; }  # if .NET gates scheduled
command -v npm >/dev/null 2>&1 || {
  command -v fnm >/dev/null 2>&1 && eval "$(fnm env --shell bash)" || true
  command -v npm >/dev/null 2>&1 && echo "preflight: self-healed via fnm activation" \
    || { echo "FAIL (preflight): npm missing"; exit 1; }
}  # if TS gates scheduled

Never pipe gate commands through tail/head/grep without set -o pipefail. The trailing command's exit code masks the real one. Read REFERENCE.md §8 "Preflight + pipefail" for safe truncation patterns.

Step 2: Run Gates

Gate 1: .NET Build (if C# changed)

dotnet build PPDS.sln -v q

Pass: 0 errors. On "used by another process", Read REFERENCE.md §2 "File-locking recovery".

Gate 2: .NET Tests (if C# changed)

dotnet test PPDS.sln --filter "Category!=Integration" -v q --no-build

Pass: 0 failures. Fail: report failing test names and assertion messages.

Gate 3: TypeScript Build (if TS/JS changed)

npm run compile --prefix src/PPDS.Extension

Pass: 0 errors.

Gate 3.5: TypeScript Type Check (if TS/JS changed)

npm run typecheck:all --prefix src/PPDS.Extension

Pass: 0 errors across host and webview tsconfigs. Read REFERENCE.md §3 "Compile vs typecheck" for why this is separate.

Gate 4: TypeScript Lint (if TS/JS changed)

npm run lint --prefix src/PPDS.Extension

Pass: 0 errors.

Gate 4.5: CSS Lint (if CSS changed)

npm run lint:css --prefix src/PPDS.Extension

Pass: 0 errors.

Gate 4.6: Dead Code Analysis (if TS/JS changed)

npm run dead-code --prefix src/PPDS.Extension

Pass: 0 unused exports.

Gate 5: TypeScript Tests (if TS/JS changed)

npm test --prefix src/PPDS.Extension

Pass: 0 failures.

Gate 5.5: TUI Snapshot Tests (if src/PPDS.Cli/Tui/ changed)

npm run tui:test

Pass: all snapshots match. Read REFERENCE.md §4 "TUI snapshot baselines" before regenerating.

Gate 6: AC Verification (if specs with ACs are relevant)

Grep specs/*.md for **Code:** lines. Match changed paths against code prefixes. For each relevant spec:

• Extract test method names from the AC table
• .NET: dotnet test --filter "FullyQualifiedName~{method}" -v q --no-build
• TS: npx vitest run -t "{method}" --prefix src/PPDS.Extension
• Report which ACs pass/fail.

Step 3: Report

Markdown table, one row per gate (PASS/FAIL/SKIP). ### Failures block listing exact errors for any FAIL. ### Verdict: PASS|FAIL. Binary - never "PASS with warnings."

Typically followed by /verify then /pr. If gates FAIL, fix first and re-run /gates before continuing.

Rules

1. Mechanical only - no subjective judgments
2. All gates run - don't skip "they probably pass"
3. Exact output - report exact errors
4. Binary verdict - PASS or FAIL
5. No fixes - report only

Read REFERENCE.md §7 "Rules (rationale)" for the why.