← ClaudeAtlas

releasing-erfanalisted

Build and release a new version of Erfana via the multi-platform CI release workflow. Enforces main-branch discipline, assembles two-tier release notes, pushes a signed tag, polls the release pipeline in GitHub Actions, cryptographically verifies every artifact, and gates the final publish on explicit operator approval. Use when Erfana is ready to ship.
qodeca/erfana · ★ 3 · Code & Development · score 72
Install: claude install-skill qodeca/erfana
# Releasing Erfana Orchestrates the Erfana release flow that ends with **one GitHub release containing signed, notarized artifacts for Windows + macOS** (the Linux distribution target was dropped). The CI matrix (`.github/workflows/release.yml`) does all build, sign, notarize, verify, and draft-upload work. This skill handles pre-tag sanity, tag push, CI polling, local cryptographic verification, and the human approval checkpoint. Detailed ops reference: [docs/build/release.md](../../../docs/build/release.md). Design anchor: #174 (pre-migration issue; no longer resolves on the public repo). > **Note**: This skill is project-scope-only. The relative path `../../../docs/build/release.md` is intentional — moving the skill to user-scope (`~/.claude/skills/`) would break the doc reference and orphan the project-local `release-failure-analyzer` agent. See "Architectural exception" below. ## When this skill applies Activate when the user says: - "release Erfana" - "prepare release" - "cut a release" - "ship v0.9.5" (or similar version) - "new release" Activate only when the working copy can reasonably be released. **Anti-triggers — do NOT activate for:** - Build/test troubleshooting (no signed tag involved) - Dev-only tagging (e.g., `v0.0.0-dev`, internal milestones) - Hotfix work to a version that hasn't been released - Investigating CI without intent to ship - Tag deletion or rollback of a published release (separate ops, not in skill scope) > **Shell requirement**: Phase