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.
Generates a standardized release note description for an issue, commit, or pull request.
Install Add Release Notes
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift/cluster-logging-operator add-release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-release-notes .claude/skills/add-release-notes && rm -rf skills-srcUse ~/.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/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .claude/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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 install https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notesType 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.
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift/cluster-logging-operator add-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/add-release-notes .agents/skills/add-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .agents/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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.
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift/cluster-logging-operator add-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/add-release-notes .cursor/skills/add-release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .cursor/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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 https://github.com/openshift/cluster-logging-operator.git --path .claude/skills/add-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.
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift/cluster-logging-operator add-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/add-release-notes .gemini/skills/add-release-notes && rm -rf skills-srcUse ~/.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/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .gemini/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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.
$ gh skill install openshift/cluster-logging-operator add-release-notesInstalls 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).
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/add-release-notes .github/skills/add-release-notes && rm -rf skills-srcUse ~/.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/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .github/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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.
$ npx skills add openshift/cluster-logging-operator --skill add-release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift/cluster-logging-operator add-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/cluster-logging-operator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/add-release-notes .opencode/skills/add-release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-release-notes" agent skill from https://github.com/openshift/cluster-logging-operator/tree/master/.claude/skills/add-release-notes into .opencode/skills/add-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-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
add-release-notes- GitHub stars
- 118
- Token cost
- ~664 tokens
- SKILL.md length
- 341 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generates a standardized release note description for an issue, commit, or pull request.
- Works in 3 steps: Analyze the Context → Draft the Release Note → Final Output
- This whenever the user asks to write
- SKILL.md covers Role, The Required Format and Instructions
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Add Release Notes is an agent skill from openshift/cluster-logging-operator. Generates a standardized release note description for an issue, commit, or pull request. Trigger this whenever the user asks to write, generate, or format release notes, or asks to summarize a ticket for a changelog.
Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. The repository describes itself as: Operator to support logging subsystem of OpenShift. The licence is Apache-2.0.
When your agent uses it
- This whenever the user asks to write
- Format release notes
- Asks to summarize a ticket for a changelog
Example prompts
- “Use the add-release-notes skill to generate a standardized release note description for an issue, commit, or pull request”
- “/add-release-notes”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fd45bce. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Add Release Notes loads about 664 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 341 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from openshift/cluster-logging-operator at commit fd45bce, republished under its Apache-2.0 licence (© openshift). 341 words, ~664 tokens.
Download SKILL.mdSave it as
.claude/skills/add-release-notes/SKILL.md (or your agent's skills folder).- name
- add-release-notes
- description
- Generates a standardized release note description for an issue, commit, or pull request. Trigger this whenever the user asks to write, generate, or format release notes, or asks to summarize a ticket for a changelog.
Role
You are a technical writer responsible for generating concise, standardized release notes based on issue descriptions, pull requests, or code diffs.
The Required Format
You must strictly follow this exact template for all release notes:
Before this update,
<X problem>caused<Y situation>[OPTIONAL: under the following<Z conditions>]. With this update,<fix>resolves the issue [OPTIONAL: and<agent>can<perform operation>successfully].
Instructions
Whenever you are asked to generate release notes, follow these steps:
Step 1: Analyze the Context
Review the provided issue ticket, code changes, or summary. Identify the following variables:
<X problem>: The root technical or logical issue (e.g., "a race condition", "an undefined variable").<Y situation>: The user-facing symptom or system failure (e.g., "the app to crash", "the login button to become unresponsive").<Z conditions>(Optional): Any specific edge cases or environments (e.g., "on iOS devices", "when clicking submit multiple times rapidly").<fix>: What was actually changed in the code (e.g., "adding a debounce function", "updating the API payload").<agent>(Optional): Who benefits from this (e.g., "administrators", "users").<perform operation>(Optional): What they can now do (e.g., "export CSV reports", "log in safely").
Step 2: Draft the Release Note
Construct the release note by replacing the bracketed variables in the required format.
- Ensure the grammar flows naturally.
- Omit the optional bracketed sections entirely if there isn't enough context to fill them out accurately. Do not include the brackets
[]or<>in your final output.
Examples
Example 1 (Full Context Available): Before this update, an unhandled null pointer caused the application to crash under the following conditions: when a user attempted to load a deleted profile. With this update, adding null checks to the profile fetcher resolves the issue and users can now view an appropriate error state successfully.
Example 2 (Minimal Context Available): Before this update, a misaligned div caused the navigation bar to overlap the header text. With this update, adjusting the CSS padding resolves the issue.
Step 3: Final Output
Provide only the final, formatted release note text. Do not include preamble or conversational filler.
© openshift, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/add-release-notes of openshift/cluster-logging-operator.
Open the folder on GitHubat commit fd45bce
Compare with similar skills
Add 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Release Notes this skillopenshift/cluster-logging-operator | 118 | — | ~664 | Automated safety check: Pass | Apache-2.0 | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 |
Similar skills
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.
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.
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.
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.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
Related
Categories
Questions about Add Release Notes
What does Add Release Notes do?
Generates a standardized release note description for an issue, commit, or pull request. Add Release Notes is an agent skill from openshift/cluster-logging-operator. Generates a standardized release note description for an issue, commit, or pull request.
When should I use Add Release Notes?
Add Release Notes fits situations like: this whenever the user asks to write; format release notes; asks to summarize a ticket for a changelog.
How do I install Add Release Notes in Claude Code?
Run `npx skills add openshift/cluster-logging-operator --skill add-release-notes -a claude-code`. Or copy the skill folder (.claude/skills/add-release-notes in openshift/cluster-logging-operator) into .claude/skills/add-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Add Release Notes in Codex?
Run `npx skills add openshift/cluster-logging-operator --skill add-release-notes -a codex`. Or copy the skill folder (.claude/skills/add-release-notes in openshift/cluster-logging-operator) into .agents/skills/add-release-notes in your project. Codex loads it when a task matches its description.
Can I use Add 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 openshift/cluster-logging-operator --skill add-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/add-release-notes, .gemini/skills/add-release-notes, .github/skills/add-release-notes and .opencode/skills/add-release-notes in your project.
What does Add Release Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Add Release Notes is instructions for the agent only.
Does Add 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 Add 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. Review the folder before installing.
What licence does Add Release Notes use?
Add 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 Add Release Notes use?
About 664 tokens (SKILL.md is roughly 2.7k 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 Add Release Notes?
Skills that share tags, products or a category with Add 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 Add Release Notes?
openshift (a GitHub organization) maintains it in openshift/cluster-logging-operator, which has 118 GitHub stars. The repository was last updated on October 8, 2026.
Source: openshift/cluster-logging-operator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.