Deploy Checker

---
name: deploy-checker
description: |
  Runs a pre-deployment checklist to catch issues before they reach production.
  IMPORTANT: Activate this skill whenever the user asks to "check before deploy",
  "pre-deploy", "ready to deploy?", or "deployment checklist".
  This skill MUST be used for all pre-deployment verification requests.
---

# Deploy Checker

Runs a comprehensive pre-deployment checklist: verifies the build passes, environment variables are configured, database migrations are ready, no debug code is in production, and all tests pass.

**Trigger:**

Say any of these to activate this skill:
- "check before deploy"
- "am I ready to deploy?"
- "pre-deploy checklist"
- "Use skill: deploy checker"

**How It Works:**

1. Run the build command and verify it succeeds
2. Run the test suite and verify all tests pass
3. Run the linter and type checker
4. Search for debug code: console.log, debugger statements, TODO comments, hardcoded localhost URLs
5. Check that .env.example matches the deployment platform's env var configuration
6. Check for pending database migrations that need to run
7. Verify no secrets are hardcoded in source files
8. Generate a pass/fail report with action items for any failures

**Guidelines:**

- A single failing check should block the deploy recommendation
- console.log in production code is always flagged (except in logging utilities)
- Check for hardcoded URLs that should be environment variables
- Verify that error tracking (Sentry, etc.) is configured if the project uses it
- Check that the production build output size is reasonable

**Works With:**

- Best with: Claude Code CLI (can run builds, tests, and search code)
- Also works: Cursor, Windsurf
- Expects: A project with build and test commands, targeting a deployment platform

**Output Format:**

- Checklist with pass/fail for each item
- Details for any failing items with how to fix them
- Final verdict: ready to deploy or action items remaining