| name | release-workflow |
| description | Execute project release workflows by locating and following project-specific RELEASE_GUIDE.md in the repository root or docs/. Use when asked to perform a release, publish a release, cut a tag, run release steps, or when a user references RELEASE_GUIDE.md. |
Release Workflow
Setup
- Load commands with
source $CLI_TOOLS/tools.sh
Workflow
- Identify the target repository root; ask if the repo path is unclear.
- Locate
RELEASE_GUIDE.mdin the repo root ordocs/:- Prefer
rg --files -g 'RELEASE_GUIDE.md'from the repo root. - If multiple guides are found, ask which one to follow.
- Prefer
- Read the entire guide before running any commands; do not infer missing steps.
- Execute steps in order, using the exact commands and tooling specified (scripts, Makefile, CI tasks, etc.).
- Follow the release guide exactly; if anything is unclear, stop and ask rather than making assumptions.
- If a step fails, stop and either follow the guide's recovery instructions or ask for user direction.
- If no
RELEASE_GUIDE.mdexists, ask the user for the correct release documentation location.
Output and clarification rules
- The response must include, in order:
- Release content (use the template provided in each project's release guide)
- Release link