deploy

name	deploy
version	1.0.0
description	Deploy the project to a hosting platform. Detects deployment configuration, runs pre-deploy checks, and guides first-time setup.
trigger	manual
depends-on	[]
references	[]
micro-components	{"pre-deploy":["discover-commands","verify-clean-git-state"]}
disable-model-invocation	true
user-invocable	true
allowed-tools	Read, Glob, Grep, Bash
argument-hint	[platform] [--dry-run]

---

deploy

Deploy the project to a hosting platform.

Arguments

• $1 (optional) — platform name override (e.g., vercel, fly, railway)
• --dry-run — show what would happen without executing

Step 1: Pre-Deploy Checks

Run the verify-clean-git-state micro-component from .claude/prompts/verify-clean-git-state.md.

Run the discover-commands micro-component from .claude/prompts/discover-commands.md.

Run tests: ```bash # Run the project's test command ``` **HALT** — "Tests are failing. Fix them before deploying — deploying broken code risks downtime for your users." Present the failure output and suggest `/debug-session` if needed.

Check git state:

• Warn if not on the default branch (but allow if user confirms)
• Warn if there are uncommitted changes

Step 2: Detect Platform

Use the specified platform. Skip auto-detection. Detect deployment configuration by checking for platform-specific files:

File / Directory	Platform
vercel.json or .vercel/	Vercel
netlify.toml or _redirects	Netlify
fly.toml	Fly.io
railway.json or railway.toml	Railway
render.yaml	Render
app.yaml (with runtime: or env:)	Google App Engine
Procfile + app.json	Heroku
amplify.yml or amplify/	AWS Amplify
Dockerfile + (docker-compose.yml or cloud config)	Container deployment

Present options: ``` No deployment configuration detected. Where would you like to deploy?

1. — best for Next.js, React, static sites. Free tier available.

```markdown ## Deployment Failed