release
Skill819 starsChanged 18 days agoApache-2.0View on GitHub
Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major".
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- contributeSkill
- create-rfcSkill
- generate-slideSkill
- propose-featureSkill
- review-prSkill
- review-rfcSkill
- update-rfcSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use grafana-product:whats-new for new or improved capabilities.
- Distinctive: line 13
Use grafana-product:whats-next for breaking changes, deprecations, removals, or disruptive behaviour changes.
- Distinctive: line 14
If both apply, prepare separate entries.
- Distinctive: line 16
Before running the release command, review the changes since the previous release to identify the required entries.
- Distinctive: line 38
After merge, tag the commit on main and push the tag:
- Very specific: line 47
If release code changes during review, rerun mise run docs:refresh -- vX.Y.Z with the upcoming version and commit the updated references to …
- Distinctive: line 54
Before declaring the release complete, report the required contributions' draft paths and CMS submission/publication status.
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Releasing gcx
Customer communications
For every major release, or minor release containing breaking changes, prepare customer communications as part of the release:
- Use grafana-product:whats-new for new or improved capabilities.
- Use grafana-product:whats-next for breaking changes, deprecations, removals, or disruptive behaviour changes.
- If both apply, prepare separate entries.
Before running the release command, review the changes since the previous release to identify the required entries. Inspect source PRs and compatibility changes rather than relying solely on commit prefixes or generated release notes. Reuse existing contributions where appropriate.
Read the relevant upstream skill and its required references, using gh to retrieve them if they are not installed. Follow their content and formatting guidance, but override their advance-notice timing: prepare the content during the release, without requiring a 2–4 week lead time or delaying the release to create one. Describe the actual release timing; do not present an already available change as upcoming.
Include affected users, exact before/after behaviour, and concrete migration instructions for breaking changes. Verify CMS metadata rather than treating a gcx version as a Grafana self-managed release version.
Release
Automated via mise run tag. Requires claude CLI; svu comes from mise install.
mise run tag -- patch # or minor, majorThis generates a changelog entry (via Claude), updates CHANGELOG.md and .release-notes.md,
and runs mise run docs:refresh -- vX.Y.Z to generate the CLI and configuration
references from the current checkout with the upcoming version. It commits these
changes together on a release/vX.Y.Z branch and pushes the branch. Then:
- Open a PR (the script prints the exact command). Review the changelog and the
generated changes to
docs/sources/cli-reference.mdanddocs/sources/configuration.md, run the repository's required checks, and merge it. - After merge, tag the commit on main and push the tag:
git checkout main && git pull git tag v0.X.Y git push origin v0.X.Y
The tag push triggers the GoReleaser workflow.
If release code changes during review, rerun mise run docs:refresh -- vX.Y.Z
with the upcoming version and commit the updated references to the same PR.
Without a version argument, mise run docs:refresh uses the latest published
stable release; use that only for standalone documentation updates.
Contribution handoff
Before declaring the release complete, report the required contributions' draft paths and CMS submission/publication status. If submission is outstanding, name the comms owner and remaining action; a local draft alone is not a submitted contribution. If no contribution is required, state why.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

