solo-deploy

# /deploy Deploy the project to its hosting platform. Reads the stack template YAML (`templates/stacks/{stack}.yaml`) for exact deploy config (platform, CLI tools, infra tier, CI/CD, monitoring), detects installed CLI tools, sets up database and environment, pushes code, and verifies deployment is live. ## Live Context - Branch: !`git branch --show-current 2>/dev/null` - Uncommitted: !`git status --short 2>/dev/null | wc -l | tr -d ' '` files - Last commit: !`git log --oneline -1 2>/dev/null` ## References - `templates/principles/dev-principles.md` — CI/CD, secrets, DNS, shared infra rules - `dev-principles-my.md` (if exists) — personal infra extensions (auth, tunnels, monitoring) - `templates/stacks/*.yaml` — Stack templates with deploy, infra, ci_cd, monitoring fields > Paths are relative to the skill's plugin root. Search for these files via Glob if not found at expected location. ## When to use After `/build` has completed all tasks (build stage is complete). This is the deployment engine. Pipeline: `/build` → **`/deploy`** → `/review` ## MCP Tools (use if available) - `session_search(query)` — find how similar projects were deployed before - `project_code_search(query, project)` — find deployment patterns across projects - `codegraph_query(query)` — check project dependencies and stack If MCP tools are not available, fall back to Glob + Grep + Read. ## Pre-flight Checks ### 0. Check if deploy is needed Read `docs/workflow.md` (if exists). If it contains "No...