pre-deploy-validator

Pre-Deploy Validator

Pre-production deployment gate: auto-detect the tech stack, run all 9 checks below, and emit a single READY / NOT READY verdict.

Hard Rules

1. Run all 9 checks — or mark a check N/A with a reason — BEFORE emitting the verdict. Never stop at the first FAIL.
2. Verdict rule: READY = zero FAIL across all 9 rows. NOT READY = one or more FAIL, with every FAIL row enumerated as a blocker. WARNs never block — list them and stay READY.
3. Every status comes from tool output you saw in this session — paste the key line(s) into Details. If a command cannot run, mark the check N/A with the reason; never guess PASS.
4. Validate only — never fix. Report blockers; do not edit code or delete artifacts.
5. Each check gets exactly one status: PASS / FAIL / WARN / N/A. Any check may be N/A when the project lacks that surface (no frontend, no migrations, no spec) — state why in Details.

Phase 0 — Load Project Context

Read if present, skip silently if absent: CLAUDE.md or AGENTS.md (build/test/lint commands, migration format, deployable components). If neither exists, fall back to README.md + directory structure. Use it to: prefer the project's documented commands over the auto-detected defaults below, and to enumerate every deployable component so each one is validated.

Phase 1 — Detect Stack & Components

Scan the project root to identify components and their verification commands:

• go.mod — Go: go vet, go test, golangci-lint (if available)
• package.json — Node.js/frontend: tsc --noEmit, npm run lint, npm run build, npm test
• requirements.txt / pyproject.toml — Python: mypy, ruff/flake8, pytest
• Cargo.toml — Rust: cargo check, cargo clippy, cargo test
• migrations/ — SQL migrations
• **/openapi.yaml — API spec

Done when: you have the component list and the command set for checks 1–4.

Phase 2 — Run the 9 Checks

Done when: every one of the 9 rows has exactly one status backed by output you saw.