skill
Ship merged code to one deploy target. Thin router: detect target, run the platform recipe, capture receipt (sha, version, URL, rollback handle), stop when healthy. Does not monitor, triage, or decide whether to deploy. Use when: "deploy", "deploy to prod", "release", "push to staging", "deploy this branch", "release cut". Trigger: /deploy, /release.
/deploy
Source: skills/deploy/SKILL.md
Ship merged code to one deploy target. Thin router: detect target, run the platform recipe, capture receipt (sha, version, URL, rollback handle), stop when healthy. Does not monitor, triage, or decide whether to deploy. Use when: "deploy", "deploy to prod", "release", "push to staging", "deploy this branch", "release cut". Trigger: /deploy, /release.
Support primitive in the Harness Kit operating loop.
This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.
Ship merged code to an environment. One invocation, one target, one
receipt. The global skill is a router; the real work lives in the
platform-specific recipe (`references/targets.md`) and repo-local config
(`references/repo-config.md`).
## Execution Stance
You are the executive orchestrator for a narrow, high-stakes action.
- Keep the abort/ship decision on the lead model. Do not delegate go/no-go.
- Delegate detection, artifact validation, and log tailing to subagents.
- Run validation steps in parallel; the deploy call itself is serial.
## Delegation Floor
Delegation floor applies for substantive deploy preparation, release-risk
review, config changes, rollback planning, or unhealthy deploy diagnosis:
probe the roster first; dispatch two or more providers; direct solo only for
mechanical deploy commands, emergency preservation, user-forbidden delegation,
or fewer-than-two-providers cases. See `harnesses/shared/AGENTS.md` (Roster).
Local lane guidance: Use specialized lanes for target detection, artifact/CI
validation, rollback-handle verification, release-risk critique, and log
interpretation. The lead owns the final deploy/abort decision and the actual
deploy command remains serial.
## Contract
**Input:** merged ref to deploy (default: current `HEAD` on primary
branch). Optional `--env` (default from repo config). Optional
`--version` (default: `HEAD` sha).
**Output:** a deploy receipt (schema below) emitted to stdout as JSON
and appended to the cycle manifest if one exists
(`.harness-kit/cycle-manifest.json`, see `/flywheel`).
**Stops at:** target reports healthy (platform-native healthcheck OR
configured `healthcheck` URL returns 2xx within `rollback_grace_seconds`).
**Does NOT:** monitor post-deploy, triage failures, rollback
automatically, build artifacts, manage secrets, promote across envs.
...