Slash Command

/deploy

Deploys app to staging/production/preview with pre/post checks. Auto-detects method (Vercel/Netlify/Docker/Kubernetes/SSH/GitHub Pages), tags deploys, verifies health, outputs status and rollback.

Vercel

npx claudepluginhub rohitg00/awesome-claude-code-toolkit

Popularity

Stars

1,720

Forks

536

Shared by

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/claude-code-toolkit:deploy

Model invocable

No pre-commands

Configuration

Namespacedevops/

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Deploy the application to a target environment with pre/post checks.

## Steps

1. Determine the target environment from the argument (staging, production, preview).
2. Run pre-deployment checks:
   - All tests pass: run the test suite.
   - No uncommitted changes: `git status --porcelain`.
   - Branch is up to date: `git fetch && git status -uno`.
   - Build succeeds: run the build command.
   - No critical vulnerabilities: run dependency audit.
3. Detect the deployment method:
   - **Vercel/Netlify**: `vercel --prod` or `netlify deploy --prod`.
   - **Docker**: Build image, push to regist...

Command Content

54 lines · ~456 tokens

Other plugins with /deploy

/deploy

Deploys to specified environment with pre-checks (git clean, tests, npm audit, build, env vars), staging first, smoke tests, monitoring, prod approval, blue-green prod deploy, report, and rollback.

3 tools

production-agents-suite

/deploy

100

Runs pre-flight checks (env validation, migrations, bundle size, ship audit), deploys the project, and performs production health check.

ultraship

/deploy

Deploys project safely through multi-gate pipeline: tests, build verification, staging deploy/verify, optional production promotion. Argument: staging|production.

/deploy

Orchestrates infrastructure deployments to <environment> with optional [strategy], rollback strategies, and health checks.

sonnet4 tools

infra-pipeline

/deploy

Executes automated deployment pipeline with pre-flight validation, staging tests, production rollout using blue-green/canary strategies, and post-deployment monitoring.

10 tools

orchestr8

/deploy

2.3k

Generates GitHub Actions workflow to build and deploy VitePress wiki site to GitHub Pages after checking for wiki directory and existing workflows.

deep-wiki

Stats

LanguageJavaScript

Stars1,720

Forks536

MaintenanceExcellent

Last CommitMay 12, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Deploy the application to a target environment with pre/post checks. ## Steps 1. Determine the target environment from the argument (staging, production, preview). 2. Run pre-deployment checks: - All tests pass: run the test suite. - No uncommitted changes: `git status --porcelain`. - Branch is up to date: `git fetch && git status -uno`. - Build succeeds: run the build command. - No critical vulnerabilities: run dependency audit. 3. Detect the deployment method: - **Vercel/Netlify**: `vercel --prod` or `netlify deploy --prod`. - **Docker**: Build image, push to regist...

Deployment: <environment> Version: <git-sha-short> Status: <success/failed> Pre-checks: - [x] Tests passing - [x] Build successful - [x] No uncommitted changes Deployed at: <timestamp> URL: <deployment-url> Health: <healthy/unhealthy> Rollback: <rollback-command>

Deploy the application to a target environment with pre/post checks.

Steps

Determine the target environment from the argument (staging, production, preview).
Run pre-deployment checks:
- All tests pass: run the test suite.
- No uncommitted changes: git status --porcelain.
- Branch is up to date: git fetch && git status -uno.
- Build succeeds: run the build command.
- No critical vulnerabilities: run dependency audit.
Detect the deployment method:
- Vercel/Netlify: vercel --prod or netlify deploy --prod.
- Docker: Build image, push to registry, update deployment.
- Kubernetes: Apply manifests with kubectl apply.
- SSH: rsync build artifacts and restart service.
- GitHub Pages: Push to gh-pages branch.
Execute the deployment:
- Tag the deployment: git tag deploy-<env>-<timestamp>.
- Run the deployment command.
- Wait for health check confirmation.
Run post-deployment verification:
- Hit the health endpoint and verify 200 response.
- Run smoke tests if available.
- Check error rates in monitoring if accessible.
Report deployment status with rollback instructions.

Format

Deployment: <environment>
Version: <git-sha-short>
Status: <success/failed>

Pre-checks:
  - [x] Tests passing
  - [x] Build successful
  - [x] No uncommitted changes

Deployed at: <timestamp>
URL: <deployment-url>
Health: <healthy/unhealthy>

Rollback: <rollback-command>

Rules

Never deploy to production from a non-default branch without explicit confirmation.
Always run pre-deployment checks; abort on any failure.
Create a deployment tag for every production deployment.
Include rollback instructions in every deployment output.
Verify the health endpoint responds within 60 seconds after deployment.

/deploy

Popularity

Invocation

Configuration

Context Preview

Command Content

Other plugins with /deploy

Help us improve

Help us improve

Find plugins for your project

/deploy

Popularity

Invocation

Configuration

Context Preview

Command Content

Steps

Format

Rules

Other plugins with /deploy

Help us improve

Steps

Format

Rules