deploy
Build the project, commit all changes, and deploy to main via the claude/merge-to-main branch. Use when deploying changes to production.
When & Why to Use This Skill
This Claude skill automates the end-to-end deployment pipeline, enabling developers to build, commit, and push changes to the production branch seamlessly. By integrating build verification with Git automation, it ensures a reliable and efficient CI/CD workflow that minimizes manual errors and accelerates the release cycle.
Use Cases
- Streamlining production releases: Automatically handle the sequence of building, staging, and pushing code to the main branch for rapid deployment.
- Pre-push build validation: Ensure the project compiles successfully by running build scripts before any changes are committed, preventing broken production environments.
- Automating repetitive Git tasks: Reduce developer friction by bundling 'git add', 'git commit', and 'git push' operations into a single, intelligent command.
- Continuous Integration support: Facilitate a smoother handoff to automated CI/CD runners by ensuring local changes are clean and properly formatted before merging.
| name | deploy |
|---|---|
| description | Build the project, commit all changes, and deploy directly to main. Use when deploying changes to production. |
| allowed-tools | Bash, Read, Glob, Write, Edit |
Deploy to Main
Automates the complete deployment workflow for pushing changes to production.
Workflow
- Build: Run
npm run buildto ensure no compilation errors - Status Check: Check git status for uncommitted changes
- Commit: Commit changes with a descriptive message
- Deploy: Push directly to main to trigger production deployment
- Confirm: Provide deployment status
Commands
# Build project
npm run build
# Check status
git status
git log --oneline -3
# Commit (if changes exist)
git add -A
git commit -m "chore: <descriptive message>"
# Push directly to main
git push origin main
When to Use
- "deploy to main"
- "push changes to production"
- "deploy these changes"
- "/deploy"