deployment
Deploy applications, configure cloud hosting targets (Vercel, Netlify, GitHub Pages, S3), manage build pipelines, and verify post-deployment health. Trigger with "deploy app", "publish release", "setu
SKILL.mdprompt-orchestrator/.claude/skills/deployment/SKILL.md
GitHub<!-- Generated from skills/deployment.md by tools/generate_integrations.py. Edit the source file, not this one. -->
Skill: Deployment
Purpose
Deploy applications, expose services, and manage release workflows.
Tools Required
- Deployment CLI tools (Netlify, Vercel, gh-pages, etc.)
- Shell commands
- Port exposure tools
General Principles
- Read deployment config before attempting to deploy
- Ensure all required files exist before deployment
- Verify build succeeds before deploy
- Check deployment status after deploying
- NEVER auto-deploy to production without user confirmation
Deployment Workflow
Pre-Deployment Checklist
- Read deployment configuration (if exists)
- Verify all source files are present
- Build succeeds locally
- Environment variables configured
- Required service accounts / API keys available
Common Platforms
| Platform | Tool | Setup |
|---|---|---|
| GitHub Pages | gh-pages package or Actions |
Push to gh-pages branch |
| Netlify | Netlify CLI / manual | Connect repo + configure build |
| Vercel | Vercel CLI | vercel for project setup |
| Static hosting | rsync / scp / s3 | Copy build output to host |
Deployment Steps
- Build the project
- If deploying new site: use project_id empty
- If updating existing site: use existing project_id
- Run deploy command
- Check deployment status
- Provide access URL to user
Service Exposure
- For temporary services: expose local ports
- For permanent services: deploy to cloud hosting
- Provide access links after deployment
- Monitor deployed applications
PR/MR Workflow
For implementation tasks in collaborative projects:
- Create feature branch from updated main
- Make changes
- Commit with descriptive message
- Push branch
- Create Pull/Merge Request
- Include summary of changes in PR description
Environment Configuration
- Use environment variables for config
- Provide .env.example file with placeholder values
- Document required environment variables
- Never commit real secrets to version control
Rollback
- Know how to roll back a deployment
- For git-based deploys: revert commit and redeploy
- For platform deploys: use platform's rollback feature
- Always keep previous deployment artifacts