release
Automated release pipeline that generates tags and PRs while enforcing human approval gates.
Install
mkdir -p .claude/skills/release-usetheodev && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12337" && unzip -o skill.zip -d .claude/skills/release-usetheodev && rm skill.zipInstalls to .claude/skills/release-usetheodev
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Cuts a semver-tagged release from develop → main after /review returns READY_TO_MERGE. Auto-derives version from CHANGELOG sections (major/minor/patch), rewrites [Unreleased] under the new version header, commits chore(release), opens a PR develop→main with rendered release notes, and waits for human approval (the only manual gate — Unbreakable Rule 4). On merge, creates an annotated tag and a GitHub release. Single entry-point for cycle-release. Use after /review {slug} returned READY_TO_MERGE.Key capabilities
- →Automate semantic version bumping based on CHANGELOG.md
- →Rewrite CHANGELOG.md to promote unreleased changes to a new version
- →Create a chore(release) commit on the develop branch
- →Open a pull request from develop to main with rendered release notes
- →Create an annotated tag and GitHub release upon PR merge
How it works
The skill validates pre-conditions, computes the next semantic version from the CHANGELOG, updates the CHANGELOG, commits the changes, and creates a pull request for human approval.
Inputs & outputs
When to use release
- →Cut a new release version
- →Automate version bumping
- →Prepare production release branch
About release
Manages the transition from develop to main branches, automatically calculates semantic versioning, updates the changelog, and creates release tags.
Cuts a semver-tagged release from develop → main after /review returns READY_TO_MERGE. Auto-derives version from CHANGELOG sections (major/minor/patch), rewrites [Unreleased] under the new version header, commits chore(release), opens a PR develop→main with rendered release notes, and waits for huma
When not to use it
- →When direct commits to main are allowed
- →When auto-merging release pull requests is desired
- →When editing CHANGELOG entries during the release process
Prerequisites
Limitations
- →It does not auto-merge the release PR
- →It requires a `READY_TO_MERGE` verdict from a `/review` run
- →It does not allow editing CHANGELOG entries during the release
How it compares
This skill automates the entire release ritual from version derivation to PR creation and tagging, while enforcing a human approval gate, unlike a manual release process.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 3mo | Review | Advanced |
| gcp-cloud-run | 5 | 7mo | Review | Intermediate |
| flow-nexus-platform | 6 | 6mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 10mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by usetheodev
View all by usetheodev →You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.