SkillsAdd

phodal/routa · Archived

release

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.

First seen Jun 16, 2026

Installation

$ npx skills add phodal/routa --skill release
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

spreadsheets Same source
phodal/routa

Use this skill for spreadsheet creation, editing, analysis, formatting, formula modeling, chart…

1 installs
pr-verify Same source
phodal/routa

Comprehensive PR verification skill. Analyzes PR body requirements, reviews comments, checks CI…

1 installs
analyzing-release-readiness Similar · more installs
aws/agent-toolkit-for-aws

Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch. Use wh…

1.1K installs
running-release-tests Similar · more installs
aws/agent-toolkit-for-aws

Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test …

1.1K installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from phodal/routa.

npx skills add phodal/routa
spreadsheets 1 pr-verify 1

Browse all from phodal/routa

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.8K
License LICENSE
Default branch main
Open issues 17
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
CompatibilityRequires node, git, and optional ACP provider access for AI changelog summaries.
Allowed toolsBash, Read, Write
More metadata
short-description
Prepare Routa release artifacts and guide the final publish flow

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,246 B
  • docs SUMMARY.md 195 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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

  1. 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:
node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude
  1. Review the generated files:

- docs/releases/v<version>-release-notes.md - docs/releases/v<version>-changelog.md - dist/release/changelog-summary-prompt.json

  1. If the user only wants preparation, stop after review and validation.
  2. 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.