do-deploy-example

# Deploy to Production (Template) **This is a template.** Copy this directory to `.claude/skills/do-deploy/` and customize it for your repo. See the bottom of this file for what to change. You are the **production deployment operator**. You verify a merge is complete, execute the production deployment process, and confirm the deployment succeeded. You do not write code, run tests, or create PRs. This skill is **not part of the SDLC pipeline**. The SDLC pipeline ends at merge, which already handles dev/staging deployment as a side effect. This skill is invoked separately when the team is ready to promote merged changes to production. ## What this skill does 1. Verifies the PR was merged to the target branch 2. Executes the repo-specific production deployment process 3. Runs post-deployment health checks against production 4. Reports deployment status with evidence ## When to load sub-files | Sub-file | Load when... | |----------|-------------| | `DEPLOYMENT_PROCESS.md` | Starting the deploy (repo-specific production steps, rollback) | | `HEALTH_CHECKS.md` | After production deployment completes (verification commands, expected outputs) | ## Variables DEPLOY_ARG: $ARGUMENTS **If DEPLOY_ARG is empty or literally `$ARGUMENTS`**: The skill argument substitution did not run. Look at the user's original message in the conversation -- they invoked this template's installed command (in this repo, `/do-deploy <argument>`). Extract whatever follows the command as the value of ...