@shipgate.dev/banned-terms-check

CI guard that fails the build when banned IntentOps terms appear in user-facing ShipGate surfaces. Catches regressions where a legacy term leaks back into the primary CLI / dashboard / docs.

Default banned terms

• Vibe Score
• Roast Me
• Prompt Builder
• Scanner warehouse
• 27 engines
• Neuro tab
• TruthPack
• AI dashboard

Usage

# Build once
$ pnpm --filter @shipgate.dev/banned-terms-check build

# Scan the monorepo
$ pnpm --filter @shipgate.dev/banned-terms-check scan

From the repo root:

$ pnpm run check:banned-terms

Allowlist

Two ways to allow an unavoidable hit:

1. Per-file allowlist entry in banned-terms.config.json:

   {
     "allowlist": [
       {
         "path": "packages/cli/src/commands/vibe.ts",
         "reason": "Legacy command — hidden under `shipgate advanced`."
       }
     ]
   }

2. Inline pragma anywhere in the file:

   <!-- shipgate-banned-terms-allow -->

Exit codes

| Code | Meaning | | ---- | ----------------------------- | | 0 | Clean scan, no banned terms. | | 1 | One or more hits found. |