release
/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.
- Author
- openai ↗
- Repository
- symphony ↗
- Licence
- Apache-2.0
- Last repository change
- 15.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
SKILL.md has no level-two headings · 25 lines, 150 words
SKILL.md preview
--- name: release description: 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. --- # Release 1. Start from fresh `origin/main` in a clean worktree. Never disturb unrelated local changes. 2. Pick the requested version. If none is given, use the next patch after the latest `vX.Y.Z` tag. 3. 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. 4. Run `make -C elixir all`, then commit, push, create a PR, and land it. 5. Fetch the merged `main` commit. Verify its `mix.exs` version, then create an annotated tag on that exact commit: ```sh git tag -a vX.Y.Z <merged-commit> -m "Symphony vX.Y.Z" git push origin vX.Y.Z ``` 6. 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · openai/symphony | 96 | Apache-2.0 |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9fc5b26a02b8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100symphony-setup
Set up Symphony (OpenAI's Codex orchestrator) for a user's repo. Use when the user mentions Symphony setup, configuring Symphony, getting Symphony running, or wants to connect their repo to Linear for autonomous Codex agents. Also use when the user says "set up symphony",… - 100version-release
Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version". - 100skills-release
Use when cutting a release of the kitaru-skills repository — pushing develop to main, bumping the kitaru plugin version, tagging a version, or publishing a GitHub Release for the Claude Code marketplace. - 100cmux-release
cmux release workflow, version bumping, changelog updates, pretag guard, release tags, and release asset expectations. Use when preparing or troubleshooting a cmux release. - 100cut-release
Cut a new agnostic-ai release end to end. Use when the user wants to ship a new version (tag + GitHub Release). - 100hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.