deploylisted

______________________________________________________________________ ## 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`. <IF condition="test command configured"> Run tests: ```bash # Run the project's test command ``` <IF condition="tests fail"> **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. </IF> </IF> 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 <IF condition="$1 provided (platform override)"> Use the specified platform. Skip auto-detection. </IF> <ELSE> 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 `ampl