team-releaselisted

Release pipeline end-to-end: perf-audit + a11y-audit + security quick check in parallel → changelog → release-checklist → deploy (via an installed deployment skill when present) → post-deploy verification. Use to ship a version.
gonimar/claude-web-studio · ★ 0 · Web & Frontend · score 76

Install: claude install-skill gonimar/claude-web-studio

# Team: Release Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" — each one `AskUserQuestion` (proceed (Recommended) · show the draft/diff first · not now) → "yes"; delegated agents follow the same protocol. After the "write" answer: `touch .claude/.write-consent` (rule 7 — the consent-guard hook checks the marker). ## Phase 1: Parallel checks `/perf-audit full` ‖ `/a11y-audit all` ‖ `/security-audit quick` ‖ `/dependency-audit`. Any FAIL → stop with a partial report. ## Phase 2: Documents `/changelog <version>` → `/release-checklist <version>`. ## Phase 3: Deploy `/deploy <version>` (confirmations inside; the delegate by `docs/deploy-target-contract.md`, manual runbook when none is declared) → smoke → monitoring. ## Phase 4: Summary Version, what shipped, post-deploy metrics, known issues; `production/stage.txt` → `operate` with consent. Verdict: `RELEASED` | `ABORTED (stage …)`. Next step — one `AskUserQuestion`: `/sprint-plan` for the next cycle (Recommended) · `/incident` if the post-deploy checks fail · stop here.