deploy-validatelisted

# Deployment Validation I'll perform comprehensive pre-deployment validation to catch issues before they reach production. **Validation Checks:** - Environment configuration - Dependency verification - Database migration status - API compatibility - Build artifacts - Security checks ## Token Optimization Strategy **Target:** 60% reduction (3,000-5,000 → 800-2,000 tokens) ### Optimization Techniques Applied #### 1. Environment Detection Caching **Pattern:** Cache environment type (dev/staging/prod) to avoid repeated detection - Store in `.claude/cache/deploy/environment.json` - Detect once per deployment context - **Savings:** 200-400 tokens per validation run #### 2. Checklist-Based Validation (Not Deep File Analysis) **Pattern:** Use Bash checks and Grep patterns instead of reading full files - Validate .env presence without reading contents - Check lock files exist without parsing dependencies - Verify build directories without analyzing artifacts - **Savings:** 1,500-2,500 tokens vs reading config files #### 3. Bash-Based Health Checks **Pattern:** Use curl/wget for endpoint checks, avoid reading application code ```bash # Good: Direct HTTP check (50 tokens) curl -f http://localhost:3000/health # Avoid: Reading route handlers to understand endpoints (800+ tokens) ``` - **Savings:** 750+ tokens per health check #### 4. Early Exit on Critical Failures **Pattern:** Stop validation immediately on security/build failures ```bash if [ $SECURITY_ISSUES -gt 0 ]; then