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.
Evaluate whether a change needs a release note. An agent skill from pingcap/docs.
Install Release Notes
$ npx skills add pingcap/docs --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pingcap/docs 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/pingcap/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .claude/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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 install https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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 pingcap/docs --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pingcap/docs release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pingcap/docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .agents/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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.
$ npx skills add pingcap/docs --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pingcap/docs release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pingcap/docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .cursor/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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 https://github.com/pingcap/docs.git --path .agents/skills/write-review-translate-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 pingcap/docs --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pingcap/docs release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pingcap/docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .gemini/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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.
$ gh skill install pingcap/docs 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 pingcap/docs --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pingcap/docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .github/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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.
$ npx skills add pingcap/docs --skill 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 pingcap/docs release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pingcap/docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-review-translate-release-notes .opencode/skills/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 "release-notes" agent skill from https://github.com/pingcap/docs/tree/master/.agents/skills/write-review-translate-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
- 616
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,103 words
- Files
- 6 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Evaluate whether a change needs a release note. An agent skill from pingcap/docs.
- Works in 4 steps: Read the backport PR first. → If the backport PR body omits details,… → Base the release note on the actual… → …
- Triaging PRs for release-note relevance
- SKILL.md covers When to use this skill, Determine whether a change…, Which reference to load and File-level structure, plus 1 more section
- Reaches github.com and docs.pingcap.com
What it does
Release Notes is an agent skill from pingcap/docs. Evaluate whether a change needs a release note. If yes, write, review, revise, or translate TiDB release note entries for the features, compatibility changes, improvements, and bug fixes sections. Use this skill when triaging PRs for release-note relevance, working with release note entries, aligning English and Chinese content, auditing release-X.X.X.md files, or editing files under docs/releases/ or docs-cn/releases/.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/bilingual-alignment.md`, `references/bug-fixes.md` and `references/compatibility-changes.md`).
It sits in Development, covering Changelog and release notes. It works with TiDB and GitHub. The repository describes itself as: TiDB database documentation. TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics.
When your agent uses it
- Triaging PRs for release-note relevance
- Working with release note entries
- Aligning English and Chinese content
- Auditing release-X.X.X.md files
Example prompts
- “/release-notes”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read the backport PR first.
- If the backport PR body omits details, follow the link to the original upstream PR and its linked issues.
- Base the release note on the actual behavior change described in the original PR or issue, not the cherry-pick mechanics.
- Ignore cherry-pick metadata (such as cherry-pick from #XXXXX) in the release note text.
What it can do on your machine
Read from SKILL.md and the folder at commit 6ba8576. 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.comdocs.pingcap.com
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 2.6k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 1,103 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 1,103 words (~2,564 tokens).
“When you evaluate whether a change needs a release note, write, review, or translate a release note entry (including feature descriptions, compatibility changes, improvements, and bug fixes), use this skill to load the right references, apply the correct patterns, and…”
- name
- release-notes
Files
SKILL.md and 5 other files (references) in .agents/skills/write-review-translate-release-notes of pingcap/docs.
- SKILL.md
- references/bilingual-alignment.md
- references/bug-fixes.md
- references/compatibility-changes.md
- references/feature-description.md
- references/improvements.md
Open the folder on GitHubat commit 6ba8576
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Notes this skillpingcap/docs | 616 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from pingcap/docs
All 8 skills in this repoAdd Related Resources
pingcap/docs
Produces and merges Related resources cards for TiDB docs pages using the RelatedResources and ResourceCard MDX components.
Create Or Update Zh Translation PR
pingcap/docs
Create or update a zh translation PR from pingcap/docs to pingcap/docs-cn by using repo-local scripts to prepare change-unit translation inputs, apply minimal edits to the existing Chinese files…
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
Writing Doc Summaries
pingcap/docs
Writes or updates the front matter summary field in pingcap/docs and pingcap/docs-cn Markdown files.
Docs Issue Metadata Guard
pingcap/docs
A skill your agent uses when creating or editing GitHub issues in pingcap/docs so issue templates, required fields, scope boundaries, and labels stay consistent with repository workflow.
Docs PR Metadata Guard
pingcap/docs
A skill your agent uses when creating or editing pull requests in pingcap/docs so the PR template sections, version checkboxes, related-link fields, HTML comments, and description structure stay…
Related
Categories
Questions about Release Notes
What does Release Notes do?
Evaluate whether a change needs a release note. An agent skill from pingcap/docs. Release Notes is an agent skill from pingcap/docs. Evaluate whether a change needs a release note.
When should I use Release Notes?
Release Notes fits situations like: triaging PRs for release-note relevance; working with release note entries; aligning English and Chinese content; auditing release-X.X.X.md files.
How do I install Release Notes in Claude Code?
Run `npx skills add pingcap/docs --skill release-notes -a claude-code`. Or copy the skill folder (.agents/skills/write-review-translate-release-notes in pingcap/docs) 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 pingcap/docs --skill release-notes -a codex`. Or copy the skill folder (.agents/skills/write-review-translate-release-notes in pingcap/docs) 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 pingcap/docs --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?
SKILL.md names no scripts, command-line tools or credentials: Release Notes is instructions for the agent only.
Does Release Notes access the network?
SKILL.md names 2 domains. In commands or code: github.com and docs.pingcap.com; the agent is likely to contact these when it follows the instructions. 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. Review the folder before installing.
What licence does Release Notes use?
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 Release Notes use?
About 2.6k tokens (SKILL.md is roughly 10k 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 12k tokens, read only when the agent opens those files.
What are the alternatives to Release Notes?
Skills that share tags, products or a category with Release Notes: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
pingcap (a GitHub organization) maintains it in pingcap/docs, which has 616 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: pingcap/docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.