Agent skill

Prepare Release

A skill your agent uses when preparing a new release. An agent skill from Gremlinq/ExRam.Gremlinq.

MITAuto-check passedDevelopment

Install Prepare Release

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-release .claude/skills/prepare-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .claude/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prepare-release .agents/skills/prepare-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .agents/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prepare-release .cursor/skills/prepare-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .cursor/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Gremlinq/ExRam.Gremlinq.git --path .agents/skills/prepare-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prepare-release .gemini/skills/prepare-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .gemini/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prepare-release .github/skills/prepare-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .github/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Gremlinq/ExRam.Gremlinq prepare-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prepare-release .opencode/skills/prepare-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "prepare-release" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/prepare-release into .opencode/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: prepare-release
GitHub stars: 187
Token cost: ~1.1k tokens
SKILL.md length: 614 words
Files: 4 (incl. scripts, references)
Skills in repo: 3
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when preparing a new release. An agent skill from Gremlinq/ExRam.Gremlinq.

Works in 4 steps: Run scripts/prerequisites.sh. Every… → **Invoke the write-release-announcements… → Run scripts/prepare.sh to bump the… → …
Preparing a new release
SKILL.md covers Usage, Workflow, What happens after this skill and Key requirements, plus 1 more section
Runs Shell scripts from its folder; calls git

What it does

Prepare Release is an agent skill from Gremlinq/ExRam.Gremlinq. Use this skill when preparing a new release. Writes the release notes and announcement texts, then bumps the version and creates the release tag. Invokes when asked to "prepare release" or similar. MUST NOT push anything to any remote.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/workflow.md`, `scripts/prepare.sh` and `scripts/prerequisites.sh`).

It sits in Development, covering Changelog and release notes. It works with Azure Cosmos DB and .NET. The repository describes itself as: A .NET object-graph-mapper for Apache TinkerPop™ Gremlin enabled databases. The licence is MIT.

When your agent uses it

Preparing a new release
Tasks that involve Changelog and release notes

Example prompts

“prepare release”
“/prepare-release”

Requirements

A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Run scripts/prerequisites.sh. Every check must pass. It reports the remote, the
**Invoke the write-release-announcements skill via the Skill tool and wait for it to
Run scripts/prepare.sh to bump the version and create the tag.
Report what to do next -- see below. Do not do it.

What it can do on your machine

Read from SKILL.md and the folder at commit b807c4b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prepare Release loads about 1.1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 614 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Gremlinq/ExRam.Gremlinq at commit b807c4b, republished under its MIT licence (© Gremlinq). 614 words, ~1,124 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-release/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: prepare-release
description: Use this skill when preparing a new release. Writes the release notes and announcement texts, then bumps the version and creates the release tag. Invokes when asked to "prepare release" or similar. MUST NOT push anything to any remote.

Prepare Release

Prepares a release of ExRam.Gremlinq: the texts first, then the version bump and the tag.

Usage

prepare release

Workflow

Run scripts/prerequisites.sh. Every check must pass. It reports the remote, the current branch and the version this release will carry.
Invoke the write-release-announcements skill via the Skill tool and wait for it to complete. It collects the pull requests merged since the previous tag, writes releases/<version>/release-notes.md plus the announcement texts, and commits them.
Run scripts/prepare.sh to bump the version and create the tag.
Report what to do next -- see below. Do not do it.

Step 2 must happen before step 3, and the reason is not stylistic. nbgv prepare-release creates a branch carrying the "Set version to 'X'" commit, and prepare.sh tags that branch and rebases the current branch onto it. The tag therefore points at the earlier of the two version commits, and anything committed afterwards is not reachable from it. In ExRam.Gremlinq, pack.yml, openAnnouncementChecklist.yml and postDiscordAnnouncement.yml all read releases/<version>/ out of the tagged commit; a repository that shares this skill but not those workflows still benefits from the same ordering, since pack.yml's release-body fallback is worse than having written the notes. Prepare the texts late and they will simply not be there.

What happens after this skill

The skill pushes nothing. Report these steps and let the user run them:

Push the tag. git push <remote> <version>. That is all the release needs to start: pack.yml triggers on the tag, builds, packs, attests, and creates a draft release whose body is releases/<version>/release-notes.md.
Review and publish the draft on GitHub. Nothing is public until then.
What publishing fires next is repository-specific -- check that repository's .github/workflows/ rather than assuming. In ExRam.Gremlinq it is pushStable.yml (NuGet.org via Trusted Publishing), publishBlogPost.yml (copies the release body into the blog on docs.gremlinq.net), openAnnouncementChecklist.yml (opens an issue with the three channel texts, ready to post) and postDiscordAnnouncement.yml (posts the .NET one by webhook, if configured). A repository that only reuses ExRam.Gremlinq's pack.yml and announce.yml via workflow_call may fire a different subset of these effects, or none of them beyond the NuGet push -- report what you can confirm, not this list by default.

The two version commits stay on the local branch and reach the release branch later, with whatever pull request is opened next. That is deliberate: the tag is what drives the release, and it carries everything the workflows read.

Show full SKILL.md (210 more words)Show less

Key requirements

MUST NOT push anything -- no branches, no tags. The user pushes the tag.
The git remote is resolved dynamically, never hardcoded: this repository also has a non-GitHub backup remote.
scripts/prepare.sh takes no arguments, and there is no choice to make here. The released version is the current preview version with its suffix dropped (14.1.2-preview.{height} releases as 14.1.2), and the branch then moves on by one build number. Preparing a release cannot produce a minor or a major.
A minor or major bump is made in the pull request that changes the public API, by raising version.json there. By the time a release is prepared the version has long been decided, so there is nothing left to decide -- and nothing prepare-release could do about it if the bump had been forgotten.
Whether this release is a patch, minor or major is reported as release_kind by write-release-announcements, which derives it by comparing the previous tag with the version being released. That is the only signal for it, and it decides whether the announcement texts are needed.
Do not write the release notes yourself. That is write-release-announcements, and it is the skill that knows the channel formats.

References

Workflow Details - what each script does, and what the release pipeline does afterwards

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/prepare-release of Gremlinq/ExRam.Gremlinq.

SKILL.md
references/workflow.md
scripts/prepare.sh
scripts/prerequisites.sh

Open the folder on GitHubat commit b807c4b

Compare with similar skills

Prepare Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prepare Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Prepare Release this skillGremlinq/ExRam.Gremlinq	187	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
.NET Release Verificationdotnet/core	22k	—	~1.8k	Automated safety check: Pass	MIT	yesterday
Add Analyzerdotnet/roslynator	3.5k	—	~1.3k	Automated safety check: Pass	Custom licence	2 days ago
Generate .NET Release changes.jsondotnet/core	22k	—	~1.7k	Automated safety check: Pass	MIT	yesterday
Release Feature Scoringdotnet/core	22k	—	~2.2k	Automated safety check: Pass	MIT	yesterday
Release Notes Editorial Reviewdotnet/core	22k	—	~1.6k	Automated safety check: Pass	MIT	yesterday

Similar skills

.NET Release Verification
dotnet/core
Official
Validates .NET release data with the release-notes CLI: download URL liveness, SHA512 hashes, CDN latest.version files and aka.ms redirects.
22k GitHub stars~1.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Add Analyzer
dotnet/roslynator
Official
A skill your agent uses when adding a new RCS diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator EditorConfig options, or when docs say CHANGELOG.md…
3.5k GitHub stars~1.3k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Generate .NET Release changes.json
dotnet/core
Official
Produces the changes.json manifest for a .NET preview, RC or GA milestone by choosing the right VMR base and head refs and running release-notes generate changes.
22k GitHub stars~1.7k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Feature Scoring
dotnet/core
Official
Ranks the changes in a release manifest and writes a scored features file that release notes, docs and blog posts can each cut at their own threshold.
22k GitHub stars~2.2k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Notes Editorial Review
dotnet/core
Official
Audits a scored features.json file and its draft release notes against editorial examples to catch over-scored, under-scored, or missing entries.
22k GitHub stars~1.6k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Roslynator
dotnet/roslynator
Official
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
3.5k GitHub stars~1k tokensUpdated 2 days ago
DevelopmentAuto-check passed

More from Gremlinq/ExRam.Gremlinq

Open Pull Request
Gremlinq/ExRam.Gremlinq
A skill your agent uses when opening a pull request for the current branch, or when an existing pull request needs a better description - including when the check-description CI check has failed.
187 GitHub stars~1.5k tokensUpdated 2 days ago
Auto-check passed
Write Release Announcements
Gremlinq/ExRam.Gremlinq
A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.
187 GitHub stars~1.5k tokensUpdated 2 days ago
Auto-check passed

Works with

Questions about Prepare Release

What does Prepare Release do?

A skill your agent uses when preparing a new release. An agent skill from Gremlinq/ExRam.Gremlinq. Gremlinq. Use this skill when preparing a new release.

When should I use Prepare Release?

Prepare Release fits situations like: preparing a new release; tasks that involve Changelog and release notes.

How do I install Prepare Release in Claude Code?

Run `npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a claude-code`. Or copy the skill folder (.agents/skills/prepare-release in Gremlinq/ExRam.Gremlinq) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.

How do I install Prepare Release in Codex?

Run `npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a codex`. Or copy the skill folder (.agents/skills/prepare-release in Gremlinq/ExRam.Gremlinq) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.

Can I use Prepare Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Gremlinq/ExRam.Gremlinq --skill prepare-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.

What does Prepare Release need to run?

Going by SKILL.md and its folder, Prepare Release needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.

Does Prepare Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prepare Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Prepare Release use?

Prepare Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prepare Release use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 919 tokens, read only when the agent opens those files.

What are the alternatives to Prepare Release?

Skills that share tags, products or a category with Prepare Release: .NET Release Verification (dotnet/core, 22k stars), Add Analyzer (dotnet/roslynator, 3.5k stars), Generate .NET Release changes.json (dotnet/core, 22k stars) and Release Feature Scoring (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Release?

Gremlinq (a GitHub organization) maintains it in Gremlinq/ExRam.Gremlinq, which has 187 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.

Source: Gremlinq/ExRam.Gremlinq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Prepare Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Prepare Release

Usage

Workflow

What happens after this skill

Key requirements

References

Files

Compare with similar skills

Similar skills

More from Gremlinq/ExRam.Gremlinq

Related

Questions about Prepare Release