ssh-deploy

name	ssh-deploy
description	This skill should be used when the user asks to "deploy to production", "restart a service", "do a rolling update", "canary deploy", "helm upgrade", or "rollout to K8s". Manual-only for safety — requires explicit /ssh-deploy invocation.
user-invocable	true
disable-model-invocation	true
argument-hint	<host> <action>
compatibility	2.1+

Deployment Operations

Deploy changes to remote infrastructure via bridge-mcp CLI. This skill is manual-only — invoke with /ssh-deploy.

Parse $ARGUMENTS: first word = host, second word = action (restart, canary, rolling, k8s, helm).

Pre-Deploy Checklist

Before ANY deployment, verify:

1. Health check — confirm the target is healthy BEFORE changing anything:

   bridge-mcp tool ssh_diagnose host=HOST --json
   

2. Confirm with user — always ask before proceeding with destructive operations.

3. Know the rollback — have a rollback command ready before executing.

Deployment Patterns

Service Restart

# Check current status
bridge-mcp tool ssh_service_status host=HOST service=SERVICE --json

# Restart
bridge-mcp tool ssh_service_restart host=HOST service=SERVICE

# Verify recovery
bridge-mcp tool ssh_service_status host=HOST service=SERVICE --json

Canary Deploy

Deploy to a single canary host first, verify, then decide:

# Execute on canary
bridge-mcp tool ssh_canary_exec host=HOST command="DEPLOY_COMMAND"

# Health check canary
bridge-mcp tool ssh_diagnose host=HOST --json

# ASK the user before continuing to remaining hosts

Rolling Deploy

Execute on one host at a time with health checks between:

bridge-mcp tool ssh_rolling_exec host=HOST command="DEPLOY_COMMAND"

Kubernetes Rollout

# Check current state
bridge-mcp tool ssh_k8s_get host=HOST resource=deployments namespace=NAMESPACE --json

# Apply update
bridge-mcp tool ssh_k8s_apply host=HOST manifest="PATH_TO_YAML" namespace=NAMESPACE

# Watch rollout
bridge-mcp tool ssh_k8s_rollout host=HOST action=status deployment=DEPLOYMENT namespace=NAMESPACE

# Rollback if needed
bridge-mcp tool ssh_k8s_rollout host=HOST action=undo deployment=DEPLOYMENT namespace=NAMESPACE

Helm Upgrade

# Check current release
bridge-mcp tool ssh_helm_status host=HOST release=RELEASE --json

# Upgrade
bridge-mcp tool ssh_helm_upgrade host=HOST release=RELEASE chart=CHART

# Verify
bridge-mcp tool ssh_helm_status host=HOST release=RELEASE --json

# Rollback if needed
bridge-mcp tool ssh_helm_rollback host=HOST release=RELEASE

Post-Deploy

After every deployment:

1. Health check — verify the system is healthy:

   bridge-mcp tool ssh_diagnose host=HOST --json
   

2. Verify service — check the specific service/app is running:

   bridge-mcp tool ssh_service_status host=HOST service=SERVICE --json
   

3. Report — tell the user: what was deployed, current status, rollback command if needed.