release
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.
Best use case
release is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using release should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/release/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How release Compares
| Feature / Agent | release | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Release Workflow
LLM主導でバージョン更新とリリースコミットを作成し、ワークフローでタグ・Release・配布を完了する。
## Preflight
- `gh auth status` が成功すること
- `git status --short` が空であること
- `origin/develop` を最新化できること
## フロー
```text
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. ローカルを最新化（必須）
```bash
git fetch origin
git pull origin develop
```
### 1. バージョン更新
```toml
[workspace.package]
version = "X.Y.Z"
```
### 2. CHANGELOG.md 更新
```markdown
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
```
### 3. リリースコミット作成
```bash
git add Cargo.toml Cargo.lock CHANGELOG.md
git commit -m "chore(release): vX.Y.Z"
git push origin develop
```
### 4. Closing Issue の収集
1. 前回タグ〜HEADのコミットからPR番号抽出
```bash
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)
```
1. 各PR本文から closing keyword 抽出
```bash
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 '^$')
```
1. PR番号を除外してIssueのみ残す
```bash
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
```
1. PR本文用に出力
```bash
for num in $REAL_ISSUES; do
echo "Closes #$num"
done
```
### 5. main へマージ
```bash
# 推奨: 既存スクリプト経由
./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.Z`
- `gh run list --workflow=publish.yml --limit 3`
- [GitHub Releases](https://github.com/akiojin/llmlb/releases)
## 注意
- バージョンは [Semantic Versioning](https://semver.org/) に従う
- `chore(release):` プレフィックスは必須（release.yml のトリガー条件）
- `gh auth login` 済みであることRelated Skills
gwt-spec-to-issue-migration
Migrate legacy spec sources to artifact-first GitHub Issue specs. Supports local `specs/SPEC-*` directories and body-canonical `gwt-spec` Issues using the bundled migration script.
gwt-pty-communication
PTY based communication tools for Project Mode orchestration (Lead/Coordinator/Developer).
gwt-pr
Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a PR body/template, or says 'open a PR/create a PR/gh pr'. Defaults: base=develop, head=current branch (same-branch only; never create/switch branches).
gwt-pr-check
Check GitHub PR status with the gh CLI, including unmerged PR detection and post-merge new-commit detection for the current branch.
gwt-fix-pr
Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Reply to ALL reviewer comments with action taken or reason for not addressing, then resolve threads. Notify reviewers after fixes.
hotfix
Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.
drawio
Create and edit draw.io diagrams in XML format. Use when the user wants to create flowcharts, architecture diagrams, sequence diagrams, or any visual diagrams. Handles XML structure, styling, fonts (Noto Sans JP), arrows, connectors, and PNG export.
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
plan
Generate a plan for how an agent should accomplish a complex coding task. Use when a user asks for a plan, and optionally when they want to save, find, read, update, or delete plan files in $CODEX_HOME/plans (default ~/.codex/plans).
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.