Menu
Use this skill to help deploy code to an environment. Triggered by "deploy", "deploy to staging", "deploy to production", "ship it".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | deploy |
| description | Use this skill to help deploy code to an environment. Triggered by "deploy", "deploy to staging", "deploy to production", "ship it". |
| argument-hint | [environment: staging|production|preview] |
| allowed-tools | Bash, Read |
| disable-model-invocation | true |
Safely deploy to $ARGUMENTS (defaults to staging if not specified).
!git status && echo "---" && git log --oneline -3
Target: $ARGUMENTS
⚠️ If deploying to production, I will explicitly confirm with you before running any deploy commands.
# Ensure clean working tree
git status
# Run tests
npm test
# Run linter
npm run lint
# Check for security issues
npm audit --audit-level=high
# Build
npm run build
Depending on your setup, deploy with one of:
# Vercel
vercel --prod # production
vercel # preview
# Railway
railway up
# Fly.io
fly deploy
# AWS (via CDK or SAM)
cdk deploy
sam deploy
# Kubernetes
kubectl apply -f k8s/ --namespace=production
# Docker Compose
docker-compose -f docker-compose.prod.yml up -d
# Heroku
git push heroku main
# GitHub Actions (trigger workflow)
gh workflow run deploy.yml --ref main -f environment=$ARGUMENTS
# Check health endpoint
curl -f https://your-app.com/health
# Tail logs for errors
# vercel logs --follow
# fly logs
# kubectl logs -f deployment/app-name
# Vercel: revert to previous deployment in dashboard
# Fly.io: fly releases list; fly deploy --image <old-image>
# Kubernetes: kubectl rollout undo deployment/app-name
# Git: git revert HEAD && git push
$ARGUMENTS
Use this skill when the user wants to create a git commit, stage files, write a commit message, or finalize their work with a git commit. Also invoked by phrases like "commit my changes", "save to git", "git commit".
Use this skill to generate, update, or improve documentation. Triggered by "write docs", "generate documentation", "update README", "document this code".
Use this skill when the user wants to review a pull request, check a PR for issues, or get feedback on a GitHub PR. Triggered by "review PR", "check PR", "review pull request", or "/review-pr <number>".
Use this skill to perform a security audit, scan for vulnerabilities, check OWASP Top 10 issues, or review code for security problems. Triggered by "security audit", "check security", "find vulnerabilities".
Use this skill to run tests, identify failures, and fix them. Triggered by "run tests", "fix failing tests", "make tests pass", or "/test".