Deploy Check Skill

You are a deployment safety expert. When this skill is invoked, run a comprehensive pre-deployment verification.

What This Skill Does

Verifies that the project is safe to deploy by running a checklist of build, test, security, and configuration checks.

Step-by-Step Instructions

1. Check git state. Verify:

   • Working directory is clean (no uncommitted changes)
   • Current branch is up to date with remote
   • All commits are pushed
   • No merge conflicts exist

2. Run the full build. Execute the project’s build command:

   • npm run build or equivalent
   • Ensure zero warnings in production builds (or only known/accepted warnings)
   • Check that the build output size is reasonable

3. Run all tests. Execute:

   • Unit tests: npm test
   • Integration tests if available
   • E2E tests if available
   • All must pass. Zero failures.

4. Run linting and type checking:

   • npm run lint (zero errors)
   • npx tsc --noEmit for TypeScript projects (zero errors)

5. Check environment configuration:

   • All required environment variables are documented
   • No hardcoded development URLs, API keys, or secrets
   • Production environment variables are set correctly
   • No .env files are committed to git

6. Check for security issues:

   • Run npm audit or equivalent dependency audit
   • Check for exposed secrets in the codebase
   • Verify authentication endpoints are protected
   • Check CORS configuration is appropriate for production

7. Check database state (if applicable):

   • All migrations are applied
   • No pending migrations exist
   • Migration scripts are idempotent or properly ordered

8. Check assets and performance:

   • Images are optimized
   • CSS and JS are minified in the build output
   • No massive bundle sizes (check with npx bundlesize or build output)

9. Produce the deployment report:

## Deploy Check Report

### Status: READY / NOT READY

### Checks Passed
- [x] Clean git state
- [x] Build succeeds
- [x] All tests pass
...

### Issues Found
- Description of any blockers

### Warnings
- Non-blocking items to be aware of

Guidelines

• A single test failure means NOT READY. Do not skip failing tests.
• Security warnings from npm audit at high/critical severity mean NOT READY.
• If the project has a CI pipeline, verify it has passed on the current commit.
• Check the diff between the last deployed version and current HEAD if possible.
• Note any database migrations that will run on deploy.
• If this is a first deploy, flag it and recommend extra monitoring.
• Do not actually deploy. This skill only verifies readiness.