Name: create-release
Author: yuya373

Prompt file imported from yuya373/claude-code-emacs (.claude/commands/create-release.md). Copyright stays with the author.

Release Command

Fetch latest tags from remote and analyze commits since the last release:
- git fetch --tags
- git log --oneline $(git describe --tags --abbrev=0)..HEAD
- git diff --stat $(git describe --tags --abbrev=0)..HEAD
Determine the appropriate version bump following semantic versioning:
- MAJOR (x.0.0): Breaking changes or major feature overhauls
- MINOR (0.x.0): New features, significant improvements, or minor breaking changes to internal APIs
- PATCH (0.0.x): Bug fixes, documentation updates, small improvements
Update version numbers in the project files:
- Run: ./scripts/update-version.sh X.Y.Z --auto-commit
- Push the commit and tag: git push && git push --tags
- IMPORTANT: Always push before creating the release to ensure --verify-tag works
Create a comprehensive release notes file that includes:
- A clear summary of what changed and why it matters
- Categorized changes (Features, Bug Fixes, Documentation, etc.)
- Any breaking changes or migration notes
- Credits to contributors if applicable
- Save the release notes to a temporary file
Execute the release script with the determined version and release notes:
- For draft release: ./scripts/create-release.sh <version> --notes-file <temp-file>
- For immediate publish: ./scripts/create-release.sh <version> --publish --notes-file <temp-file>
Open the created release in the browser for review:
- For draft releases: gh release view <version> --web
- This allows you to review and edit the release before publishing

Install create-release and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Release Command\n\n1. Fetch latest tags from remote and analyze commits since the last release:\n - `git fetch --tags`\n - `git log --oneline $(git describe --tags --abbrev=0)..HEAD`\n - `git diff --stat $(git describe --tags --abbrev=0)..HEAD`\n\n2. Determine the appropriate version bump following semantic versioning:\n - MAJOR (x.0.0): Breaking changes or major feature overhauls\n - MINOR (0.x.0): New features, significant improvements, or minor breaking changes to internal APIs\n - PATCH (0.0.x): Bug fixes, documentation updates, small improvements\n\n3. Update version numbers in the project files:\n - Run: `./scripts/update-version.sh X.Y.Z --auto-commit`\n - Push the commit and tag: `git push && git push --tags`\n - **IMPORTANT**: Always push before creating the release to ensure --verify-tag works\n\n4. Create a comprehensive release notes file that includes:\n - A clear summary of what changed and why it matters\n - Categorized changes (Features, Bug Fixes, Documentation, etc.)\n - Any breaking changes or migration notes\n - Credits to contributors if applicable\n - Save the release notes to a temporary file\n\n5. Execute the release script with the determined version and release notes:\n - For draft release: `./scripts/create-release.sh <version> --notes-file <temp-file>`\n - For immediate publish: `./scripts/create-release.sh <version> --publish --notes-file <temp-file>`\n\n6. Open the created release in the browser for review:\n - For draft releases: `gh release view <version> --web`\n - This allows you to review and edit the release before publishing", "variables": [], "notes": "1. Fetch latest tags from remote and analyze commits since the last release: - `git fetch --tags` - `git log --oneline $(git describe --tags --abbrev=0)..HEAD` - `git diff --stat $(git describe --tags --abbrev=0)..HEAD`", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/yuya373/claude-code-emacs", "path": ".claude/commands/create-release.md", "ref": "ebc13e87c4c04e5df2c486c118570e1076fbc945", "url": "https://github.com/yuya373/claude-code-emacs/blob/ebc13e87c4c04e5df2c486c118570e1076fbc945/.claude/commands/create-release.md", "key": "yuya373/claude-code-emacs/.claude/commands/create-release.md" } } }

create-release

About

Release Command

Use it

Install create-release and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews