deploylisted

# deploy — commit → deploy → monitor → verify → repeat A delivery-execution skill for projects where deployment is driven from the repo (a tag, a branch push, a CI dispatch, or a deploy command). It runs once by default, or loops autonomously until the exit condition is met. It is deliberately **configuration-driven**: nothing below assumes a specific CI provider, orchestrator, or cloud. | Usage | What it does | |-------|-------------| | `/deploy` | Commit + push (+ merge to the integration branch) + trigger the deployment | | `/deploy fix: use internal URL` | Same, with a custom commit description | | `/deploy commit-only` | Commit + push only — no merge, no deploy | | `/deploy no-deploy` | Commit + push + merge, skip the deploy trigger | | `/deploy setup` | (Re-)run the interview and rewrite `.claude/config/deploy.yaml` | | `/deploy loop` | Full ship loop: implement → commit → deploy → monitor → verify → test → repeat | --- ## Step 0 — Load or build the delivery profile Read `.claude/config/deploy.yaml`. If it exists, use it and **ask nothing** already answered. If it is missing (or `setup` mode), build it: **auto-detect first, ask only what detection can't settle**, then write the file so the interview never repeats. ### What to detect / ask 1. **Integration branch** — the branch deployments are cut from (staging/SIT/release), if any. Detect: a branch named in `CLAUDE.md`, or the branch recent merge commits target. Trunk-based projects answer "none — deploy fr