Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.
Install Review Release Notes
$ npx skills add chef/chef-web-docs --skill review-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install chef/chef-web-docs review-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/chef/chef-web-docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/review-release-notes .claude/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .claude/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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/chef/chef-web-docs/tree/main/.github/skills/review-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 chef/chef-web-docs --skill review-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install chef/chef-web-docs review-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chef/chef-web-docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/review-release-notes .agents/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .agents/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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 chef/chef-web-docs --skill review-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install chef/chef-web-docs review-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chef/chef-web-docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/review-release-notes .cursor/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .cursor/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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/chef/chef-web-docs.git --path .github/skills/review-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 chef/chef-web-docs --skill review-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install chef/chef-web-docs review-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chef/chef-web-docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/review-release-notes .gemini/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .gemini/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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 chef/chef-web-docs review-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 chef/chef-web-docs --skill review-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/chef/chef-web-docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/review-release-notes .github/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .github/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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 chef/chef-web-docs --skill review-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 chef/chef-web-docs review-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chef/chef-web-docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/review-release-notes .opencode/skills/review-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 "review-release-notes" agent skill from https://github.com/chef/chef-web-docs/tree/main/.github/skills/review-release-notes into .opencode/skills/review-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-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
review-release-notes- GitHub stars
- 143
- Token cost
- ~5.2k tokens
- SKILL.md length
- 2,822 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.
- Works in 5 steps: Determine available inputs → Parse the release notes file → Fetch Jira release issues → …
- : review release notes
- SKILL.md covers What to ask the user, Stage 0: Determine available…, Stage 1: Parse the release… and Stage 2: Fetch Jira release…, plus 3 more sections
- Reaches github.com and progresssoftware.atlassian.net
What it does
Review Release Notes is an agent skill from chef/chef-web-docs. Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources. If entries are already drafted, review and improve them using the available source data; if not, add new sections. If no sources are provided, edit the file for style and structure only. Uses read-only Atlassian and GitHub MCP operations. Never create, update, or delete anything in GitHub or Jira. Triggers on: review release notes, update release notes, fix release notes, release notes from PRs…
Its SKILL.md is about 5.2k 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 and Pull requests. It works with Jira, GitHub and Model Context Protocol. The repository describes itself as: All The Documentation.
When your agent uses it
- : review release notes
- Update release notes
- Fix release notes
- Release notes from PRs
Example prompts
- “/review-release-notes”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Determine available inputs
- Parse the release notes file
- Fetch Jira release issues
- Fetch pull request details from GitHub
- Edit the release notes
What it can do on your machine
Read from SKILL.md and the folder at commit e0c87d0. 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 (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.comprogresssoftware.atlassian.net
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
Review Release Notes loads about 5.2k tokens when it runs. Until then it costs about 159 tokens; SKILL.md has 2,822 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,822 words (~5,202 tokens).
“Runs a five-stage workflow to review a release notes file using Jira release data and GitHub pull requests as optional sources. If entries for the release are already drafted, the skill reviews and improves them using the available source data…”
- name
- review-release-notes
- argument-hint
- Path to the release notes file. Optionally add one or both sources: docs/release-notes.md https://example.atlassian.net/projects/CHEF/versions/43153/tab/releas…
Files
Just SKILL.md in .github/skills/review-release-notes of chef/chef-web-docs.
Open the folder on GitHubat commit e0c87d0
Compare with similar skills
Review 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 |
|---|---|---|---|---|---|---|
| Review Release Notes this skillchef/chef-web-docs | 143 | — | ~5.2k | Automated safety check: Pass | Custom licence | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Link Ticket To SessionJayantDevkar/claude-code-karma | 329 | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Create Epic RecapDataDog/datadog-agent | 3.8k | — | ~5k | Automated safety check: Notes | Apache-2.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Plannotator Release Preparationbacknotprop/plannotator | 9.2k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Link Ticket To Session
JayantDevkar/claude-code-karma
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.
- Official
Create Epic Recap
DataDog/datadog-agent
A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Plannotator Release Preparation
backnotprop/plannotator
Drafts Plannotator release notes with full contributor credit, bumps versions in dependency order, builds, and starts the tag-driven release pipeline, in four reviewed phases.
Ansible Pull Request Review
ansible/ansible
Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests.
More from chef/chef-web-docs
Fix Broken Links
chef/chef-web-docs
Run linkchecker against a locally served site, a deployed URL, or a local HTML build output, parse the errors, map each broken link back to its Markdown source file, suggest replacement URLs, and…
Alt Text Edit
chef/chef-web-docs
Scan a Markdown file for images, audit every alt text value against accessibility and style guidelines, view each image in the workspace, draft accurate alt text, and edit the file in place.
Related
Works with
Categories
Questions about Review Release Notes
What does Review Release Notes do?
Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources. Review Release Notes is an agent skill from chef/chef-web-docs. Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.
When should I use Review Release Notes?
Review Release Notes fits situations like: : review release notes; update release notes; fix release notes; release notes from PRs.
How do I install Review Release Notes in Claude Code?
Run `npx skills add chef/chef-web-docs --skill review-release-notes -a claude-code`. Or copy the skill folder (.github/skills/review-release-notes in chef/chef-web-docs) into .claude/skills/review-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Review Release Notes in Codex?
Run `npx skills add chef/chef-web-docs --skill review-release-notes -a codex`. Or copy the skill folder (.github/skills/review-release-notes in chef/chef-web-docs) into .agents/skills/review-release-notes in your project. Codex loads it when a task matches its description.
Can I use Review 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 chef/chef-web-docs --skill review-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/review-release-notes, .gemini/skills/review-release-notes, .github/skills/review-release-notes and .opencode/skills/review-release-notes in your project.
What does Review Release Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Release Notes is instructions for the agent only.
Does Review Release Notes access the network?
SKILL.md names 2 domains. In commands or code: github.com and progresssoftware.atlassian.net; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Review 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 Review Release Notes use?
Review Release Notes has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Review Release Notes use?
About 5.2k tokens (SKILL.md is roughly 21k 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 Review Release Notes?
Skills that share tags, products or a category with Review Release Notes: Plane Release Notes Generator (makeplane/plane, 61k stars), Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars), Create Epic Recap (DataDog/datadog-agent, 3.8k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Release Notes?
chef (a GitHub organization) maintains it in chef/chef-web-docs, which has 143 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: chef/chef-web-docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.