Cursor rule

1---
2description: "Build → verify artifact → deploy → wait → smoke deployment pipeline. Platform-agnostic (MCP or CLI), with configurable timeout, retry with exponential backoff, and integrated health-check. The deploy half of CI/CD: run after build to push to production."
3alwaysApply: false
4---
5 
6# Deploy
7 
8> **HARD GATE** — Do not deploy without running tests first. Run `test` or your CI suite before this skill.
9>
10> **HARD GATE** — Use this skill from a CI/CD pipeline or post-merge on `main`/`master`. Never deploy from a feature branch.
11>
12> **HARD GATE** — The deploy skill orchestrates deployment; the `smoke-test` skill validates post-deploy health. Chain them: `deploy → smoke-test`.
13 
14Orchestrate a full build-to-deployment pipeline: build the artifact, verify it exists and is non-empty, invoke a platform deploy tool (MCP or CLI), poll until the deploy completes or times out, then run a baseline smoke test against the live URL.
15 
16## Pipeline Stages
17 
18```
19build → verify artifact → deploy → wait/retry → smoke
20```
21 
22| Stage | Description | Failure mode |
23|-------|-------------|-------------|
24| Build | Execute the project's build command | Non-zero exit: report build error |
25| Verify | Check artifact exists and is non-empty | Missing/empty: report artifact path |
26| Deploy | Invoke platform deploy tool (MCP, Vercel CLI, rsync, etc.) | Non-zero exit: report deploy error |
27| Wait | Poll deploy status every 30s up to `DEPLOY_TIMEOUT` (default 5 min) | Timeout: report exceeded |
28| Smoke | `curl -sSf $DEPLOY_URL` as baseline health check | Non-200: report failure |
29 
30## Process
31 
32### 1. Detect build command
33 
34Read project manifest files in order to determine the build command:
35 
36| Manifest | Build command |
37|----------|--------------|
38| `package.json` | `npm run build` (or `scripts.build` value) |
39| `Cargo.toml` | `cargo build --release` |
40| `pyproject.toml` / `setup.py` | Depends on build backend (`poetry build`, `pip install -e .`, etc.) |
41| `Makefile` | `make build` or first target named `build` |
42| `AGENTS.md` / `CLAUDE.md` | Look for `build:` in project commands section |
43 
44If no manifest is found, prompt the user with: "No detected build command. Pass `--build 'npm run build'` or specify the command."
45 
46### 2. Build the artifact
47 
48```bash
49npm run build
50```
51 
52Or the detected command from step 1. If the build fails, exit non-zero and report the build output.
53 
54### 3. Verify the artifact
55 
56```bash
57ARTIFACT_DIR="${ARTIFACT_DIR:-dist}"
58if [ ! -d "$ARTIFACT_DIR" ] || [ -z "$(ls -A "$ARTIFACT_DIR" 2>/dev/null)" ]; then
59  echo "FAIL: build artifact not found at $ARTIFACT_DIR"
60  exit 1
61fi
62```
63 
64Configurable via `$ARTIFACT_DIR` environment variable (default: `dist/`).
65 
66### 4. Deploy to platform
67 
68Platform-agnostic — supports multiple deployment targets via environment variables:
69 
70| Platform | Env var | Example |
71|----------|---------|---------|
72| Vercel | `VERCEL_TOKEN`, `VERCEL_PROJECT_ID` | `vercel deploy --prod --token $VERCEL_TOKEN` |
73| Netlify | `NETLIFY_AUTH_TOKEN`, `NETLIFY_SITE_ID` | `netlify deploy --prod --auth $NETLIFY_AUTH_TOKEN --dir $ARTIFACT_DIR` |
74| Platform MCP | MCP tool call | `mcp deploy` via your platform MCP server |
75| rsync/SSH | `DEPLOY_SSH_USER`, `DEPLOY_SSH_HOST`, `DEPLOY_SSH_PATH` | `rsync -avz $ARTIFACT_DIR/ $DEPLOY_SSH_USER@$DEPLOY_SSH_HOST:$DEPLOY_SSH_PATH` |
76| Custom | `DEPLOY_COMMAND` | Run any deploy command string |
77 
78The deploy tool is selected by which environment variables are set. If none are configured:
79 
80```bash
81echo "No deploy target configured. Set one of: VERCEL_TOKEN, NETLIFY_AUTH_TOKEN, DEPLOY_SSH_USER+DEPLOY_SSH_HOST, DEPLOY_COMMAND, or MCP deploy tool."
82exit 1
83```
84 
85### 5. Wait and poll status
86 
87After invoking the deploy command, poll for completion:
88 
89See [REFERENCE.md](REFERENCE.md)
90 
91Use exponential backoff for retries on transient failures:
92 
93See [REFERENCE.md](REFERENCE.md)
94 
95### 6. Baseline smoke test
96 
97See [REFERENCE.md](REFERENCE.md)
98 
99For comprehensive health-checking, chain to the `smoke-test` skill:
100 
101```bash
102# After deploy success
103bash scripts/run-smoke.sh "$DEPLOY_URL"
104```
105 
106### 7. Three-independent-facts verification (e45s15)
107 
108Before declaring deploy success, verify **three independent facts** — build artifact, platform accept, live/registry reachability. See [REFERENCE.md](REFERENCE.md#three-independent-facts).
109 
110## Verify
111 
112→ verify: `command -v curl >/dev/null 2>&1 && test -f skills/smoke-test/SKILL.md`
113 
114---
115 
116# Deploy — Reference
117 
118## Configuration
119 
120| Variable | Default | Description |
121|----------|---------|-------------|
122| `ARTIFACT_DIR` | `dist` | Build output directory |
123| `DEPLOY_URL` | *(required)* | Live URL for smoke test |
124| `DEPLOY_TIMEOUT` | `300` | Max wait for deploy completion (seconds) |
125| `DEPLOY_POLL_INTERVAL` | `30` | Polling interval (seconds) |
126| `RETRY_MAX` | `3` | Max deploy retry attempts |
127| `BUILD_COMMAND` | *(auto-detect)* | Override build command |
128 
129 
130---
131 
132## Verification
133 
134→ verify: `test -f deploy/SKILL.md && grep -q 'name: deploy' deploy/SKILL.md && echo OK`
135→ verify: `grep -qi 'build\|artifact\|deploy\|smoke' deploy/SKILL.md && echo OK`
136→ verify: `grep -ci 'package.json\|Cargo.toml\|Makefile\|manifest' deploy/SKILL.md | awk '{if($1>=1) print "OK"; else print "FAIL"}'`
137→ verify: `grep -ci 'timeout\|poll\|status\|retry\|backoff' deploy/SKILL.md | awk '{if($1>=2) print "OK"; else print "FAIL"}'`
138→ verify: `grep -q 'curl.*DEPLOY_URL\|smoke\|health' deploy/SKILL.md && echo OK`
139 
140---
141 
142## Reference block 1
143 
144```bash
145DEPLOY_TIMEOUT="${DEPLOY_TIMEOUT:-300}"   # seconds (default 5 minutes)
146DEPLOY_POLL_INTERVAL="${DEPLOY_POLL_INTERVAL:-30}"  # seconds
147 
148start_time=$(date +%s)
149while true; do
150  elapsed=$(( $(date +%s) - start_time ))
151  if [ "$elapsed" -ge "$DEPLOY_TIMEOUT" ]; then
152    echo "FAIL: deploy status polling timed out after ${DEPLOY_TIMEOUT}s"
153    exit 1
154  fi
155  
156  status=$(get_deploy_status)  # platform-specific status check
157  if [ "$status" = "ready" ] || [ "$status" = "done" ]; then
158    echo "Deploy completed in ${elapsed}s"
159    break
160  fi
161  
162  sleep "$DEPLOY_POLL_INTERVAL"
163done
164```
165 
166---
167 
168## Reference block 2
169 
170```bash
171RETRY_MAX="${RETRY_MAX:-3}"
172base_delay=2
173for attempt in $(seq 1 "$RETRY_MAX"); do
174  if deploy_command; then
175    break
176  fi
177  if [ "$attempt" -eq "$RETRY_MAX" ]; then
178    echo "FAIL: deploy failed after ${RETRY_MAX} attempts"
179    exit 1
180  fi
181  sleep $(( base_delay * 2 ** (attempt - 1) ))
182done
183```
184 
185---
186 
187## Reference block 3
188 
189```bash
190DEPLOY_URL="${DEPLOY_URL:?DEPLOY_URL must be set}"
191if curl -sSf "$DEPLOY_URL" > /dev/null 2>&1; then
192  echo "OK: $DEPLOY_URL responds with HTTP 200"
193else
194  echo "FAIL: $DEPLOY_URL is not responding with HTTP 200"
195  exit 1
196fi
197```
198