diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 8f021a8..5e7faca 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -81,7 +81,14 @@ jobs:
           CURRENT_TAG="${GITHUB_REF_NAME}"
           PREV_TAG=$(git describe --tags --abbrev=0 ${CURRENT_TAG}^ 2>/dev/null || echo "")
 
-          if [ -n "$PREV_TAG" ]; then
+          # Get the full commit message body of the release commit
+          # (the empty commit created by /create-release)
+          COMMIT_HASH=$(git rev-list -n 1 ${CURRENT_TAG})
+          BODY=$(git log -1 --format=%b ${COMMIT_HASH})
+
+          if [ -n "$BODY" ]; then
+            echo "$BODY" > release-notes.md
+          elif [ -n "$PREV_TAG" ]; then
             echo "## Changes since ${PREV_TAG}" > release-notes.md
             echo "" >> release-notes.md
             git log --oneline ${PREV_TAG}..${CURRENT_TAG} >> release-notes.md
diff --git a/.opencode/command/create-release.md b/.opencode/command/create-release.md
new file mode 100644
index 0000000..21d59a1
--- /dev/null
+++ b/.opencode/command/create-release.md
@@ -0,0 +1,35 @@
+---
+description: Create and push a release tag (e.g. /create-release 1.0.0)
+---
+
+Create a release tag and push it to origin. The GitHub Action will automatically build for all platforms and create the GitHub Release.
+
+## Steps
+
+1. Validate the version argument ($ARGUMENTS):
+   - Must be provided, otherwise show error and stop
+   - Must match semver format (e.g. 1.0.0, 0.9.1, 2.0.0-beta.1)
+
+2. Check for uncommitted changes:
+   - Run `git status --porcelain`
+   - If any output, warn the user and stop (commit first)
+
+3. Analyze changes since last release:
+   - Run `git log --oneline $(git describe --tags --abbrev=0 HEAD)..HEAD` to list all commits
+   - Read the changed files to understand context
+   - Write a concise, well-structured release summary in English with:
+     - A one-line overview
+     - Bullet points for each notable change (features, fixes, breaking changes)
+     - Keep it developer-friendly, no fluff
+
+4. Create release commit with the summary as message:
+   - Run `git commit --allow-empty -m "release v$ARGUMENTS\n\n<summary>"`
+   - The commit message IS the release notes — the GitHub Action picks it up automatically
+
+5. Create annotated tag on that commit:
+   - Run `git tag -a v$ARGUMENTS -m "Release v$ARGUMENTS"`
+
+6. Push commit and tag:
+   - Run `git push origin main --tags` (or current branch)
+
+7. Confirm success with the version number