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:

# 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

npx tsc --noEmit

Expected: No errors

Status	Action
PASS	Continue to 1.2
FAIL	STOP - Fix type errors

1.2 Production Build

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

npm run test

Expected: All tests green

2.2 E2E Tests (optional but recommended)

npm run test:e2e

Expected: Critical flows working

---

PHASE 3: No-Touch Zones Check (BLOCKING)

Check if protected files were modified:

# Replace with your no-touch zones
git diff --name-only HEAD~1 | grep -E "(auth|core|production)"

Expected: No matches (or explicit approval present)

File Pattern	Modification Allowed?
**/auth/**	ONLY with explicit request
**/core/**	ONLY with explicit request
config/production.*	ONLY with explicit request

---

PHASE 4: Region/Environment Check (BLOCKING on Deploy)

4.1 Before Production Deploy

Verify deployment target matches requ...