Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.
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.
Review the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a Git commit from current changes using the session history to explain their purpose. The skill checks which files belong, stages the intended work, and writes a structured message covering changes, rationale, and validation.
Investigate stalled, retrying, or failed Symphony runs by connecting Linear issue identifiers with Codex sessions. Trace log events in time order, identify the failing stage, and collect evidence for the probable cause.
Guide a pull request through conflict resolution, review feedback, and automated checks. The skill monitors progress, fixes failures, and completes a squash merge, combining the branch’s changes into one commit once checks and reviews are addressed.
Work with Linear issues through Symphony’s authenticated client. Retrieve issue details, update workflow states, create or edit comments, link GitHub pull requests, and upload videos using GraphQL, an API language for requesting specific data.
Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.
Publish the current Git branch to origin and create or update its pull request, a request to review and merge changes. The skill runs validation and refreshes the title and description to match the full scope.