Menu
Prepare a versioned release notes document for the Firely CQL SDK. Use when the user asks to write, draft, or cut release notes for a new version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Address code review comments (e.g. from Copilot's automated PR review) on an open PR, then mark each resolved conversation. Use after a reviewer leaves inline comments and you've fixed and pushed the corresponding changes.
Tick off completed acceptance-criteria checkboxes in a linked issue/ticket or PR body after finishing and pushing the corresponding work. Use right after pushing commits to a PR, before reporting the task as done.
Write or update a GitHub PR description for this repo. Use when the user asks to create, update, or improve a pull request's description/body.
Create or edit a GitHub issue for this repo. Use when the user asks to file a bug, write up an issue, or edit an existing issue's body.
Regenerate ELM JSON files after adding or changing CQL input files in a test/library-set project (e.g. CoreTests/Input/ELM/HL7). Use when the user adds CQL files and needs the corresponding ELM generated.
Pick up a GitHub issue/ticket by number or URL — find or create its branch and check it out. Use when the user says to pick up, start, or work on a specific ticket/issue number.
| name | cut-release-notes |
| description | Prepare a versioned release notes document for the Firely CQL SDK. Use when the user asks to write, draft, or cut release notes for a new version. |
tl;dr format, product-area grouping, and "Common Items To Check" list.FirelyNetVersion) and the old/new value.docs/releases/release-notes-<version>.md.VersionPrefix (the SDK version) is being bumped as part of this release, also update the ## Release Notes section of README.md — it has a line like "This is release version X.Y.Z of the engine." that must stay in sync.docs/releases/vnext-release-notes.md into it — that file's content is pre-drafted material for exactly this purpose and must not be left behind.docs/releases/vnext-release-notes.md back to the empty template, ready for the next cycle:# vNext Release Notes
## Breaking Changes
## Features
## Fixes
Note: breaking changes should already be landing in vnext-release-notes.md as part of the PRs that introduce them (see root CLAUDE.md) — this skill is about turning that accumulated content into a versioned release, not about discovering breaking changes from scratch.