Menu
Cut an Elixir named release with the canonical release script, verification, and live announcement audit
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Analyze elixir-v5.log for errors, recurring failures, and operational signals, then recommend concrete actions
Create a new system signal announcement for the clan in Elixir
Assess the live v5.1 awareness loop from thoughts, delivered posts, stream coverage, tool traces, and incidents
Cross-check live Clash Royale API payloads stored in raw_api_payloads against docs/cr-api-docs/ and recommend concrete documentation patches — undocumented fields, new enum values, type or nullability drift, shape changes
Analyze the llm_calls table in elixir-v51.db to break down Elixir's LLM spend by workflow, model, and day; identify cost drivers; recommend signal-side or model-tier cuts
| name | new-release |
| description | Cut an Elixir named release with the canonical release script, verification, and live announcement audit |
Elixir releases use a coined Clash Royale name, date, and build hash — not
SemVer. scripts/cut_release.py is the canonical ceremony. It gathers changes,
coins or accepts a name, generates detailed/Discord/clan-chat tiers, updates
RELEASES.md and agent/core.py, commits, pushes, tags, creates the GitHub
release, records durable memory, emails the clan, and posts the announcement.
Do not hand-edit version constants or add a startup system signal for an
ordinary release. The old RELEASE_VERSION/capability_unlock checklist is
retired.
AGENTS.md and verify the worktree and branch.--since REF or --days N).Always inspect the generated three-tier copy before publishing:
uv run python scripts/cut_release.py --dry-run --since <ref>
The user may supply the coined name:
uv run python scripts/cut_release.py --dry-run --since <ref> --name "Blazing Balloon"
If no name is supplied, the script coins one. Report it for review before the non-dry-run cut when the user has not already authorized autonomous publishing.
uv run python scripts/cut_release.py --since <ref> --name "Blazing Balloon"
Use --no-email or --no-announce only when explicitly requested or when that
surface is unavailable. To retry only a failed Discord announcement after the
release itself succeeded:
uv run python scripts/cut_release.py --announce-only blazing-balloon
After the script returns:
RELEASE_CODENAME and RELEASE_STAMP in agent/core.py.RELEASES.md.Never rerun a full cut merely because one best-effort notification failed. Report the release label, commit, tag, GitHub URL, delivery results, and live build verification.
$ARGUMENTS