Agent skill

Release Notes

Generate release notes for an OpenShift Local release in a text file following a pre-defined format

Apache-2.0Auto-check passedDevelopment

Install Release Notes

skills CLI

$ npx skills add crc-org/crc --skill release-notes -a claude-code

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

GitHub CLI

$ gh skill install crc-org/crc release-notes --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/crc-org/crc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-notes .claude/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .claude/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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/crc-org/crc/tree/main/.agents/skills/release-notes

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 crc-org/crc --skill release-notes -a codex

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

GitHub CLI

$ gh skill install crc-org/crc release-notes --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/crc-org/crc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-notes .agents/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .agents/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 crc-org/crc --skill release-notes -a cursor

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

GitHub CLI

$ gh skill install crc-org/crc release-notes --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/crc-org/crc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-notes .cursor/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .cursor/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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/crc-org/crc.git --path .agents/skills/release-notes

--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 crc-org/crc --skill release-notes -a gemini-cli

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

GitHub CLI

$ gh skill install crc-org/crc release-notes --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/crc-org/crc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-notes .gemini/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .gemini/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 crc-org/crc release-notes

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 crc-org/crc --skill release-notes -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/crc-org/crc.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-notes .github/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .github/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 crc-org/crc --skill release-notes -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 crc-org/crc release-notes --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/crc-org/crc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-notes .opencode/skills/release-notes && 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 "release-notes" agent skill from https://github.com/crc-org/crc/tree/main/.agents/skills/release-notes into .opencode/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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: release-notes
GitHub stars: 1.4k
Token cost: ~1.1k tokens
SKILL.md length: 497 words
Files: 4 (incl. scripts)
Skills in repo: 2
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Generate release notes for an OpenShift Local release in a text file following a pre-defined format

Works in 3 steps: Verify we are in the crc source code… → Verify gh CLI is available → Ensure the tag for the release is…
Tasks that involve Changelog and release notes
SKILL.md covers Pre-flight Checks, Gather Release Information, Extract Version Information and Generate Release Notes, plus 2 more sections
Runs Python scripts from its folder

What it does

Release Notes is an agent skill from crc-org/crc. Generate release notes for an OpenShift Local release in a text file following a pre-defined format

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 (for example `examples/sample.md`, `scripts/verify.py` and `template.md`).

It sits in Development, covering Changelog and release notes. The repository describes itself as: CRC is a tool to help you run containers. It manages local VMs to run a OpenShift 4.x cluster, Microshift or Podman optimized for testing and development purposes. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Changelog and release notes

Example prompts

“/release-notes”

Requirements

Python 3

Workflow steps

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

Verify we are in the crc source code repository by checking
Verify gh CLI is available
Ensure the tag for the release is checked out (e.g., tag name: v2.58.0)

What it can do on your machine

Read from SKILL.md and the folder at commit 854b65c. 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 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Release Notes loads about 1.1k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 497 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~28
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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 crc-org/crc at commit 854b65c, republished under its Apache-2.0 licence (© crc-org). 497 words, ~1,105 tokens.

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

name: release-notes
description: Generate release notes for an OpenShift Local release in a text file following a pre-defined format
disable-model-invocation: true
argument-hint: release-tag
effort: low

To prepare the release notes for an OpenShift Local (crc) release:

Pre-flight Checks

Verify we are in the crc source code repository by checking:
bash
```
grep -q "github.com/crc-org/crc" go.mod
```

Verify gh CLI is available:

bash

command -v gh >/dev/null || { echo "ERROR: gh CLI not installed" >&2; exit 1; }

Ensure the tag for the release is checked out (e.g., tag name: v2.58.0):
bash
```
git describe --exact-match --tags
```
If not on a release tag, abort with an error message.

Gather Release Information

Determine the current release tag and automatically find the previous tag:

bash

CURRENT_TAG=$(git describe --exact-match --tags)
PREV_TAG=$(git describe --tags --abbrev=0 ${CURRENT_TAG}^)

Get all git logs between the previous tag and current tag:
bash
```
git log --pretty="%H %s" ${PREV_TAG}..${CURRENT_TAG}
```
From the commit descriptions, ignore commits that match these patterns:
- build(deps): - dependency updates
- chore(deps): - dependency updates
- test: or ^.*test.*$ - test-only changes
- ci: - CI/CD configuration changes
- docs: - documentation-only changes
- Any commit message indicating non-user-facing changes
Keep commits that are user-facing, such as:
- feat: - new features
- fix: - bug fixes
- perf: - performance improvements
- refactor: - code refactoring with user impact
For each relevant commit, get additional context from the associated Pull Request:
bash
```
PR_NUMBER=$(gh pr list --search "<COMMIT-SHA>" --state merged --json "number" --jq ".[].number")
```
If no PR is found, try searching by commit message keywords or check if the commit was part of a squashed merge.
Get PR details including title, body, and labels:
bash
```
gh pr view ${PR_NUMBER} --json "title,body,labels" --jq '{title, body, labels: [.labels[].name]}'
```
Use labels to identify breaking changes, features, or bug fixes if available.

Extract Version Information

Extract the OpenShift and MicroShift bundle versions from the Makefile:

bash

OPENSHIFT_VERSION=$(grep "^OPENSHIFT_VERSION" Makefile | cut -d'=' -f2 | tr -d ' ')
MICROSHIFT_VERSION=$(grep "^MICROSHIFT_VERSION" Makefile | cut -d'=' -f2 | tr -d ' ')

Determine the semantic version number for the release:

bash

CRC_VERSION=${CURRENT_TAG#v}  # Remove 'v' prefix from tag

Validate all required template variables are available:
- ${CRC_VERSION} - numeric version (e.g., 2.58.0)
- ${CURRENT_TAG} - git tag with 'v' prefix (e.g., v2.58.0)
- ${OPENSHIFT_VERSION} - OpenShift bundle version
- ${MICROSHIFT_VERSION} - MicroShift bundle version

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

Generate Release Notes

Create descriptive summaries for each user-facing change:
- Keep each summary between 10-15 words
- Focus on user impact, not implementation details
- Reference the issue number or PR number in brackets (e.g., [4], [5])
Strictly follow the template format from template.md and write the release notes to:
```
Output file: crc-release-notes-${CRC_VERSION}.txt
Example: crc-release-notes-2.58.0.txt
```
Place the file in the repository root directory.

Validation

Verify the generated release notes match the expected format in sample.md:
- Check Subject line format
- Verify all version placeholders are replaced
- Ensure bullet points are properly formatted
- Confirm all reference links [0] through [n] are present and sequential

Verify all URLs are valid and return HTTP 200:

bash

cat crc-release-notes-${CRC_VERSION}.txt | python3 .claude/skills/release-notes/scripts/verify.py

Post-Generation Summary

Provide a summary including:
- Total number of commits reviewed
- Number of user-facing changes included in release notes
- List of PRs/issues referenced
- Confirmation that all URLs are valid
- Output file location
- Next steps: "Review the release notes and send via email"

Files

SKILL.md and 3 other files (scripts) in .agents/skills/release-notes of crc-org/crc.

SKILL.md
examples/sample.md
scripts/verify.py
template.md

Open the folder on GitHubat commit 854b65c

Compare with similar skills

Release Notes 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.

Release Notes compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Notes this skillcrc-org/crc	1.4k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
StarRocks Release NotesStarRocks/starrocks	12k	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Cutting A ReleaseTriliumNext/Trilium	38k	—	~3.2k	Automated safety check: Pass	AGPL-3.0	today
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Mole CLI Release Flowtw93/Mole	69k	—	~2.5k	Automated safety check: Pass	GPL-3.0	today

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
12k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check: notes
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
69k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
28k GitHub stars~2.9k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Release Notes

What does Release Notes do?

Generate release notes for an OpenShift Local release in a text file following a pre-defined format. Release Notes is an agent skill from crc-org/crc.

When should I use Release Notes?

Release Notes fits situations like: tasks that involve Changelog and release notes.

How do I install Release Notes in Claude Code?

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

How do I install Release Notes in Codex?

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

Can I use Release Notes 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 crc-org/crc --skill release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.

What does Release Notes need to run?

Going by SKILL.md and its folder, Release Notes needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Release Notes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Release Notes 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 Release Notes use?

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

How many tokens does Release Notes use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Notes?

Skills that share tags, products or a category with Release Notes: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes?

crc-org (a GitHub organization) maintains it in crc-org/crc, which has 1,389 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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

Release Notes

Install Release Notes

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

Pre-flight Checks

Gather Release Information

Extract Version Information

Generate Release Notes

Validation

Post-Generation Summary

Files

Compare with similar skills

Similar skills

Simple English

StarRocks Release Notes

Cutting A Release

React Router Release Notes Prep

Mole CLI Release Flow

Release

More from crc-org/crc

E2E Test

Questions about Release Notes

Install Release Notes

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

Pre-flight Checks

Gather Release Information

Extract Version Information

Generate Release Notes

Validation

Post-Generation Summary

Files

Compare with similar skills

Similar skills

Simple English

StarRocks Release Notes

Cutting A Release

React Router Release Notes Prep

Mole CLI Release Flow

Release

More from crc-org/crc

E2E Test

Related

Questions about Release Notes