release
Automates the full software release lifecycle.
Install
mkdir -p .claude/skills/release-akiojin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16527" && unzip -o skill.zip -d .claude/skills/release-akiojin && rm skill.zipInstalls to .claude/skills/release-akiojin
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.
Execute the release workflow when the user asks `release` or `/release`: sync develop, update version/changelog, create `chore(release)` commit, collect closing issues, create develop->main release PR, and verify release/publish artifacts.Key capabilities
- →Synchronize local `develop` branch with `origin/develop`
- →Update version numbers in `Cargo.toml` and `CHANGELOG.md`
- →Create a `chore(release): vX.Y.Z` commit
- →Collect closing issues from previous pull requests
- →Create a pull request from `develop` to `main` for release
- →Verify release and publish artifacts on GitHub
How it works
The skill automates the release process by updating versions, committing changes, collecting issue information, and creating a release pull request. It then verifies the creation of GitHub releases and published artifacts.
Inputs & outputs
When to use release
- →Perform a new release
- →Update project version and changelog
- →Merge develop to main for release
About this skill
Release Workflow
LLM主導でバージョン更新とリリースコミットを作成し、ワークフローでタグ・Release・配布を完了する。
Preflight
gh auth statusが成功することgit status --shortが空であることorigin/developを最新化できること
フロー
release (/release) 実行
↓
① origin/develop を pull してローカルを最新化
↓
② バージョン更新(Cargo.toml, CHANGELOG.md)
↓
③ chore(release): vX.Y.Z コミット作成
↓
④ Closing Issue を収集
↓
⑤ develop → main マージ(PR本文に Closing Issues 記載)
↓
⑥ release.yml がタグ作成 → GitHub Release作成
↓
⑦ publish.yml がバイナリビルド → Release にアタッチ
手順
0. ローカルを最新化(必須)
git fetch origin
git pull origin develop
1. バージョン更新
[workspace.package]
version = "X.Y.Z"
2. CHANGELOG.md 更新
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
3. リリースコミット作成
git add Cargo.toml Cargo.lock CHANGELOG.md
git commit -m "chore(release): vX.Y.Z"
git push origin develop
4. Closing Issue の収集
- 前回タグ〜HEADのコミットからPR番号抽出
LAST_TAG=$(git describe --tags --abbrev=0)
PR_NUMBERS=$(git log ${LAST_TAG}..HEAD --oneline \
| grep -oE '(#[0-9]+)|\bMerge pull request #[0-9]+' \
| grep -oE '[0-9]+' | sort -u)
- 各PR本文から closing keyword 抽出
CLOSING_ISSUES=""
for pr in $PR_NUMBERS; do
BODY=$(gh pr view "$pr" --json body -q '.body' 2>/dev/null || true)
ISSUES=$(echo "$BODY" \
| grep -oiE '(close[sd]?|fix(e[sd])?|resolve[sd]?)\s+#[0-9]+' \
| grep -oE '[0-9]+' || true)
CLOSING_ISSUES="$CLOSING_ISSUES $ISSUES"
done
CLOSING_ISSUES=$(echo "$CLOSING_ISSUES" | tr ' ' '\n' | sort -u | grep -v '^$')
- PR番号を除外してIssueのみ残す
REAL_ISSUES=""
for num in $CLOSING_ISSUES; do
IS_PR=$(gh api "repos/{owner}/{repo}/issues/$num" \
--jq 'has("pull_request") and .pull_request != null' 2>/dev/null || echo "false")
if [ "$IS_PR" = "false" ]; then
REAL_ISSUES="$REAL_ISSUES $num"
fi
done
- PR本文用に出力
for num in $REAL_ISSUES; do
echo "Closes #$num"
done
5. main へマージ
# 推奨: 既存スクリプト経由
./scripts/prepare-release.sh
# または prepare-release workflow を直接起動
gh workflow run prepare-release.yml
# 手動PR作成の場合
gh pr create --base main --head develop \
--title "chore(release): vX.Y.Z"
6. 配布確認
gh release view vX.Y.Zgh run list --workflow=publish.yml --limit 3- GitHub Releases
注意
- バージョンは Semantic Versioning に従う
chore(release):プレフィックスは必須(release.yml のトリガー条件)gh auth login済みであること
When not to use it
- →When `gh auth status` is not successful
- →When `git status --short` is not empty
- →When `origin/develop` cannot be updated
Limitations
- →Requires `gh auth status` to be successful
- →Requires `git status --short` to be empty
- →Requires `origin/develop` to be up-to-date
How it compares
This skill provides a structured, automated release workflow that includes version bumping, changelog updates, issue collection, and PR creation, 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 | 5mo | Review | Intermediate |
| release-prep | 0 | 3mo | Review | Beginner |
| release-prep | 0 | 3mo | No flags | Intermediate |
| sdk-release-checklist | 0 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by akiojin
View all by akiojin →You might also like
release-prep
Fu-Jie
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
release-prep
NickCrew
Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.
sdk-release-checklist
macalbert
>-
pdlc-deploy
kanfu-panda
创建部署文档
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