Name: create-release
Author: zafnz

Prompt file imported from zafnz/simgadget (.cursor/commands/create-release.md). Copyright stays with the author.

Create GitHub Release from Changes Since Last Tag

Create a GitHub release based on commits since the previous tag. Generate release notes, create the release using the GitHub CLI, and verify the post-release workflow status.

Gather Information

Get the new version from packages/simgadget/package.json version key — both packages publish in lockstep at the same version, and the workspace root is private and carries none
Get the previous tag using git describe --tags --abbrev=0
Get the target commit SHA using git rev-parse HEAD

Steps

Get Git Diff: Look at all the changes between the previous tag and HEAD:
```
git --no-pager diff <PREVIOUS_REF>
```

Format Release Notes: Take the raw git diff and format it into Markdown using this structure:

# SimGadget <NEW_VERSION>

## Features 
- **Feature Name:** Description...

## Improvements
- **Improvement Name:** Description...

## Documentation
- **Doc Update:** Description...

## Build
- **Version Bump:** Updated the project version to <NEW_VERSION>.

Create Temporary Notes File: Save the formatted markdown notes into TEMP.md. This avoids shell quoting/escaping issues.

⚠️ STOP and ask for review before proceeding. Creating a release will trigger a GitHub action that is too fast to cancel if triggered by mistake.
Create GitHub Release: Use the gh CLI to create the release:
```
gh release create <NEW_VERSION> --target <TARGET_SHA> --title "<RELEASE_TITLE>" --notes-file TEMP.md --latest
```
For the title, use format: <NEW_VERSION> - <SUMMARY> where summary is the most significant change in 5 words or less. Consider adding an emoji at the end if it matches well.
Clean Up: Remove the temporary notes file:
```
rm TEMP.md
```
Verify Workflow Status: Check the status of the workflow run triggered by the release:
```
gh run list --limit 1 --json name,status,conclusion,event,url --jq '.[0]' | cat
```
The conclusion field should be success.

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.

# Create GitHub Release from Changes Since Last Tag Create a GitHub release based on commits since the previous tag. Generate release notes, create the release using the GitHub CLI, and verify the post-release workflow status. ## Gather Information 1. **Get the new version** from `packages/simgadget/package.json` version key — both packages publish in lockstep at the same version, and the workspace root is private and carries none 2. **Get the previous tag** using `git describe --tags --abbrev=0` 3. **Get the target commit SHA** using `git rev-parse HEAD` ## Steps 1. **Get Git Diff:** Look at all the changes between the previous tag and HEAD: ```bash git --no-pager diff <PREVIOUS_REF> ``` 2. **Format Release Notes:** Take the raw git diff and format it into Markdown using this structure: ```markdown # SimGadget <NEW_VERSION> ## Features - **Feature Name:** Description... ## Improvements - **Improvement Name:** Description... ## Documentation - **Doc Update:** Description... ## Build - **Version Bump:** Updated the project version to <NEW_VERSION>. ``` 3. **Create Temporary Notes File:** Save the formatted markdown notes into `TEMP.md`. This avoids shell quoting/escaping issues. ⚠️ **STOP and ask for review before proceeding.** Creating a release will trigger a GitHub action that is too fast to cancel if triggered by mistake. 4. **Create GitHub Release:** Use the `gh` CLI to create the release: ```bash gh release create <NEW_VERSION> --target <TARGET_SHA> --title "<RELEASE_TITLE>" --notes-file TEMP.md --latest ``` For the title, use format: `<NEW_VERSION> - <SUMMARY>` where summary is the most significant change in 5 words or less. Consider adding an emoji at the end if it matches well. 5. **Clean Up:** Remove the temporary notes file: ```bash rm TEMP.md ``` 6. **Verify Workflow Status:** Check the status of the workflow run triggered by the release: ```bash gh run list --limit 1 --json name,status,conclusion,event,url --jq '.[0]' | cat ``` The `conclusion` field should be `success`.

{ "prompt": "# Create GitHub Release from Changes Since Last Tag\n\nCreate a GitHub release based on commits since the previous tag. Generate release notes, create the release using the GitHub CLI, and verify the post-release workflow status.\n\n## Gather Information\n\n1. **Get the new version** from `packages/simgadget/package.json` version key — both packages publish in lockstep at the same version, and the workspace root is private and carries none\n2. **Get the previous tag** using `git describe --tags --abbrev=0`\n3. **Get the target commit SHA** using `git rev-parse HEAD`\n\n## Steps\n\n1. **Get Git Diff:**\n Look at all the changes between the previous tag and HEAD:\n ```bash\n git --no-pager diff <PREVIOUS_REF>\n ```\n\n2. **Format Release Notes:**\n Take the raw git diff and format it into Markdown using this structure:\n ```markdown\n # SimGadget <NEW_VERSION>\n\n ## Features \n - **Feature Name:** Description...\n\n ## Improvements\n - **Improvement Name:** Description...\n\n ## Documentation\n - **Doc Update:** Description...\n\n ## Build\n - **Version Bump:** Updated the project version to <NEW_VERSION>.\n ```\n\n3. **Create Temporary Notes File:**\n Save the formatted markdown notes into `TEMP.md`. This avoids shell quoting/escaping issues.\n\n ⚠️ **STOP and ask for review before proceeding.** Creating a release will trigger a GitHub action that is too fast to cancel if triggered by mistake.\n\n4. **Create GitHub Release:**\n Use the `gh` CLI to create the release:\n ```bash\n gh release create <NEW_VERSION> --target <TARGET_SHA> --title \"<RELEASE_TITLE>\" --notes-file TEMP.md --latest\n ```\n \n For the title, use format: `<NEW_VERSION> - <SUMMARY>` where summary is the most significant change in 5 words or less. Consider adding an emoji at the end if it matches well.\n\n5. **Clean Up:**\n Remove the temporary notes file:\n ```bash\n rm TEMP.md\n ```\n\n6. **Verify Workflow Status:**\n Check the status of the workflow run triggered by the release:\n ```bash\n gh run list --limit 1 --json name,status,conclusion,event,url --jq '.[0]' | cat\n ```\n The `conclusion` field should be `success`.", "variables": [], "notes": "Create a GitHub release based on commits since the previous tag. Generate release notes, create the release using the GitHub CLI, and verify the post-release workflow status.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zafnz/simgadget", "path": ".cursor/commands/create-release.md", "ref": "3a8225ea7255a9f92fc6366409350e96fbec34bc", "url": "https://github.com/zafnz/simgadget/blob/3a8225ea7255a9f92fc6366409350e96fbec34bc/.cursor/commands/create-release.md", "key": "zafnz/simgadget/.cursor/commands/create-release.md" } } }

create-release

About

Create GitHub Release from Changes Since Last Tag

Gather Information

Steps

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

Use it

Manifest

Reviews