ship-gate

原文涵盖的主题

• Ship Gate
• Intercept Behavior
• How It Works
• Step 1: Detect Stack
• Step 2: Run Automated Checks
• Step 3: Manual Confirmation
• Step 4: Verdict
• Categories

Pre-production audit that scans a codebase and reports pass/fail/manual across 8 categories before anything ships. When the user says "push to production", "deploy", "ship it", "go live", or similar deploy-intent phrases, do NOT proceed with deployment. Instead: 1. Ask: "Have you run the ship gate? Want me to scan now?" 2. If yes, run the full audit below. 3. If the user says they already ran it, ask when. If more than 24 hours ago or if code changed since, recommend re-running. Run these checks in order to identify the project stack: Report detected stack before proceeding. This determines which checks are relevant. Checks tagged with a specific stack in references/checks.md are skipped if that stack is not detected. Run categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS. Security and database first because they produce the most critical findings. For each category, run every auto-scannable check from references/checks.md using the patterns in references/patterns.md. Report progress after each category completes: Report results as: PASS: check passed FAIL: issue found (with file path and line number) SKIP: not applicable to this stack For checks that cannot be autom

这里只展示节选，请以完整原文和当前要求为准。