← ClaudeAtlas

qa-checklistlisted

Formal Quality Assurance Checklist before every Merge/Deploy. 6-phase validation with Build Verification, Test Suite, No-Touch Zones, Region Check, Security Review, and QA Report generation. Activate on "merge", "deploy", "release", "production", or /qa command.
freitasp1/claude-code-skills · ★ 8 · Testing & QA · score 68
Install: claude install-skill freitasp1/claude-code-skills
# QA Checklist > Formal Quality Assurance Checklist before every Merge/Deploy ## Trigger This skill activates automatically on: - `git commit` (after production code changes) - Deploy commands (`vercel --prod`, `npm run deploy`, etc.) - `/qa` command - Trigger words: "merge", "deploy", "release", "production" --- ## Configuration Customize these values for your project: ```yaml # Add to your project's CLAUDE.md or settings no_touch_zones: - "src/auth/**" # Authentication logic - "src/core/**" # Core business logic - "config/production.*" # Production config required_region: "your-region" # e.g., fra1, us-east-1 deploy_timeout: 60 # seconds ``` --- ## PHASE 1: Build Verification (BLOCKING) ### 1.1 TypeScript Compilation ```bash npx tsc --noEmit ``` **Expected:** No errors | Status | Action | |--------|--------| | PASS | Continue to 1.2 | | FAIL | STOP - Fix type errors | ### 1.2 Production Build ```bash npm run build ``` **Expected:** Build successful, no warnings | Status | Action | |--------|--------| | PASS | Continue to Phase 2 | | FAIL | STOP - Fix build errors | --- ## PHASE 2: Test Suite (BLOCKING) ### 2.1 Unit Tests ```bash npm run test ``` **Expected:** All tests green ### 2.2 E2E Tests (optional but recommended) ```bash npm run test:e2e ``` **Expected:** Critical flows working --- ## PHASE 3: No-Touch Zones Check (BLOCKING) Check if protected files were modified: ```bash # Replace with your no-t