mcpbeat

Release

openai/release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

295 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
26423
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/openai/symphony --skill release

The instruction itself

1 sections, as written by the author

Release

  • Start from fresh origin/main in a clean worktree. Never disturb unrelated

local changes.

  • Pick the requested version. If none is given, use the next patch after the

latest vX.Y.Z tag.

  • Update elixir/mix.exs so version: "X.Y.Z" matches the intended tag.

Search the old version and change other files only when they are true

release-version sources, not examples.

  • Run make -C elixir all, then commit, push, create a PR, and land it.
  • Fetch the merged main commit. Verify its mix.exs version, then create an

annotated tag on that exact commit:

   git tag -a vX.Y.Z <merged-commit> -m "Symphony vX.Y.Z"
   git push origin vX.Y.Z
  • Watch burrito-release until it finishes. Verify the build, smoke, and

release jobs pass and that the GitHub release has all expected assets.

Do not tag an uncommitted or unmerged revision. Do not move a published tag

without explicit user approval.

How to use it

Copy the folder

Take openai/release from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.