How do I install the Release skill?

Run npx skillmds@latest add phodal/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Release?

phodal (@phodal) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by phodal — Agent Skill

Name: Release
Author: phodal

File contents

Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.

When to use

The user asks to release Routa, publish a version, prepare release notes, or generate a release blog post.
The task needs synchronized version bumps plus docs/releases/ artifacts.

Workflow

Confirm the target version and whether the user wants a dry run or an actual publish.
If a release summary already exists, pass it with --summary-file. If the user wants AI-generated summary copy, add --ai and optionally --ai-provider <name>.
Run the helper:

node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude

Review the generated files:
- docs/releases/v<version>-release-notes.md
- docs/releases/v<version>-changelog.md
- dist/release/changelog-summary-prompt.json
If the user only wants preparation, stop after review and validation.
If the user wants to publish, continue with either:

./scripts/release/publish.sh <version>

or the manual flow documented in docs/release-guide.md.

Guardrails

Do not tag or push without explicit user confirmation.
Do not discard unrelated worktree changes.
Prefer docs/releases/v<version>-release-notes.md as the blog/release-note source of truth after generation.
If git status --porcelain is not clean and the task is a real publish, call that out before invoking publish.sh.

References

Read references/release-workflow.md for the step-by-step release decision tree.
Read docs/release-guide.md when the task needs the full publish or verification checklist.

---name: releasedescription: Automate the Routa release preparation workflow from version sync through release note and blog generation. Use when the user wants to prepare, publish, or dry-run a Routa release.license: MIT---Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.## When to use- The user asks to release Routa, publish a version, prepare release notes, or generate a release blog post.- The task needs synchronized version bumps plus `docs/releases/` artifacts.## Workflow1. Confirm the target version and whether the user wants a dry run or an actual publish.2. If a release summary already exists, pass it with `--summary-file`. If the user wants AI-generated summary copy, add `--ai` and optionally `--ai-provider <name>`.3. Run the helper:```bashnode scripts/release/prepare-release-artifacts.mjs <version>node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude```4. Review the generated files: - `docs/releases/v<version>-release-notes.md` - `docs/releases/v<version>-changelog.md` - `dist/release/changelog-summary-prompt.json`5. If the user only wants preparation, stop after review and validation.6. If the user wants to publish, continue with either:```bash./scripts/release/publish.sh <version>```or the manual flow documented in `docs/release-guide.md`.## Guardrails- Do not tag or push without explicit user confirmation.- Do not discard unrelated worktree changes.- Prefer `docs/releases/v<version>-release-notes.md` as the blog/release-note source of truth after generation.- If `git status --porcelain` is not clean and the task is a real publish, call that out before invoking `publish.sh`.## References- Read `references/release-workflow.md` for the step-by-step release decision tree.- Read `docs/release-guide.md` when the task needs the full publish or verification checklist.

Frequently asked questions

Release