| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-04-25T00:00:00.000Z" |
| reviewed | "2026-04-25T00:00:00.000Z" |
| allowed-tools | Read, Write, Edit, Bash(git *), Bash(gh release *), Bash(gh pr *), TodoWrite |
| args | <version> [--draft] [--prerelease] |
| argument-hint | <version> [--draft] [--prerelease] |
| disable-model-invocation | true |
| description | Create and publish releases via release-please or manual GitHub releases. Use when cutting a release, tagging a version, or setting up release-please config. |
| name | deploy-release |
Release Creation Command
Create GitHub releases using release-please automation or manual release workflows for containerized applications.
When to Use This Skill
| Use this skill when... | Use deploy-handoff instead when... |
|---|
Cutting a new release from main and tagging a version | Documenting an already-deployed service for another developer or client |
| Setting up or auditing release-please automation and manifests | Generating access URLs, monitoring links, and onboarding checklists for a deployed resource |
| Publishing a manual GitHub release, draft, or pre-release | Producing handoff prose for a ticket rather than cutting a version |
| Driving the version-tag side of a containerized release pipeline | Building or hardening container images themselves (use container-development) |
Context
- Git remotes: !
git remote -v
- Branch: !
git branch --show-current
- Recent tags: !
git tag --sort=-v:refname -l 'v*' --format='%(refname:short)' -n5
- Last release commit: !
git log --oneline --max-count=5
- Release config: !
find . -maxdepth 1 -name 'release-please-config.json'
- Manifest: !
find . -maxdepth 1 -name '.release-please-manifest.json'
- Changelog: !
find . -maxdepth 1 -name 'CHANGELOG.md'
Parameters
Parse from $ARGUMENTS:
$1 (VERSION): Semantic version string (e.g., 1.2.0, v2.0.0-rc.1)--draft: Create release as draft (not published)--prerelease: Mark as pre-release
Execution
Execute this release workflow:
Step 1: Determine release strategy
Check whether the project uses release-please or manual releases:
- If
release-please-config.json exists, use the release-please workflow
- If no release-please config exists, use the manual release workflow
Step 2a: Release-please workflow
