From 7dca82baa893c5dc855b5320d117c8a91f8f9e27 Mon Sep 17 00:00:00 2001
From: Stefan Koelle <stefan.koelle@gmail.com>
Date: Tue, 11 Aug 2026 00:54:10 +0200
Subject: [PATCH] /create-release in README.md

---
 README.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/README.md b/README.md
index 04368f8..a705973 100644
--- a/README.md
+++ b/README.md
@@ -183,6 +183,16 @@ This builds the project, generates a structured `.demo/` directory with sample f
 Releases are automated via GitHub Actions (`.github/workflows/release.yml`).
 
 **To create a release:**
+
+You can use the `/create-release` command (via opencode) for a fully automated flow:
+
+```text
+/create-release 1.0.0
+```
+
+This command validates the version, checks for uncommitted changes, generates a release summary from recent commits, creates a release commit with the summary as the commit message, tags it, and pushes — all in one step. The GitHub Action then builds platform ZIPs and creates the GitHub Release.
+
+**Manual release:**
 1. Ensure `README.md` and `AGENTS.md` are up to date.
 2. Commit all changes.
 3. Tag and push: