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.
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Install React Router Release Notes Prep
$ npx skills add remix-run/react-router --skill prepare-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install remix-run/react-router prepare-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/remix-run/react-router.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-release-notes .claude/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .claude/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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/remix-run/react-router/tree/main/.agents/skills/prepare-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 remix-run/react-router --skill prepare-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install remix-run/react-router prepare-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prepare-release-notes .agents/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .agents/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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 remix-run/react-router --skill prepare-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install remix-run/react-router prepare-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prepare-release-notes .cursor/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .cursor/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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/remix-run/react-router.git --path .agents/skills/prepare-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 remix-run/react-router --skill prepare-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install remix-run/react-router prepare-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prepare-release-notes .gemini/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .gemini/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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 remix-run/react-router prepare-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 remix-run/react-router --skill prepare-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prepare-release-notes .github/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .github/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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 remix-run/react-router --skill prepare-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 remix-run/react-router prepare-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prepare-release-notes .opencode/skills/prepare-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 "prepare-release-notes" agent skill from https://github.com/remix-run/react-router/tree/main/.agents/skills/prepare-release-notes into .opencode/skills/prepare-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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
prepare-release-notes- GitHub stars
- 57k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 444 words
- Files
- 3 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
- Works in 5 steps: Inspect local state → Read every pending change file. Do not… → Normalize each change file → …
- Polishing pending change files before a React Router release
- SKILL.md covers Workflow, Change File Style and What's Changed Guidance
- Calls pnpm and git
What it does
Before the changes and versioning scripts run, the agent checks git status, lists the pending change files under packages/*/.changes, reads every one, and never edits generated changelogs or released notes directly. It normalizes each file: removing feat and fix semantic-commit prefixes, using imperative or present tense for the first line and top-level bullets, dropping terminal periods because release generation appends PR or commit links after the first line, and splitting multi-sentence bullets into a short parent plus nested details.
It then decides whether scripts/changes/whats-changed.md is needed. That file is for features, future-flag stabilizations, unstable flags, migration guidance, breaking bug fixes or complex behavior that needs long-form text, and not for ordinary bug fixes, dependency cleanup or internal refactors. The release script adds the What's Changed heading, so only the body is written. Last, the agent runs pnpm changes:validate and changes:preview to check the generated notes, and says so when a command was skipped. A whats-changed reference file and an OpenAI agent config are included.
When your agent uses it
- Polishing pending change files before a React Router release
- Removing semantic-commit prefixes from release bullets
- Deciding whether a release needs a long-form What's Changed section
- Drafting release notes for new features or stable and unstable flags
Example prompts
- “Normalize the pending change files under packages/*/.changes so they use imperative tense.”
- “Do we need a whats-changed.md section for this release, or are the bullets enough?”
- “Draft the long-form notes for the stabilized future flag and run the preview.”
Requirements
- pnpm, with the repository's changes:validate and changes:preview scripts
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Inspect local state
- Read every pending change file. Do not edit generated changelogs or released notes directly.
- Normalize each change file
- Review whether scripts/changes/whats-changed.md is needed
- Validate
What it can do on your machine
Read from SKILL.md and the folder at commit 266915e. 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
Shell commands in SKILL.md call:
pnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and 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
React Router Release Notes Prep loads about 1.1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 444 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 remix-run/react-router at commit 266915e, republished under its MIT licence (© remix-run). 444 words, ~1,126 tokens.
Download SKILL.mdSave it as
.claude/skills/prepare-release-notes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- prepare-release-notes
- description
- Prepare React Router release notes before running the changes/versioning scripts. Use when asked to review, polish, normalize, or prepare pending change files under packages/*/.changes, remove semantic commit prefixes from release bullets, enforce imperative tense, decide whether a manual scripts/changes/whats-changed.md section is warranted, or draft long-form release notes for new features, stable future flags, or unstable flags.
Prepare Release Notes
Polish pending React Router change files and add manual release notes only when the release needs narrative context beyond the generated change lists.
Workflow
- Inspect local state:
git status --short
find packages -path '*/.changes/*.md' -not -name README.md -not -name .gitkeep -print | sortRead every pending change file. Do not edit generated changelogs or released notes directly.
Normalize each change file:
- Remove
feat:,feat(...),fix:, andfix(...)semantic-commit prefixes from prose - Use present or imperative tense for the first line and top-level release bullets: prefer
Add,Fix,Remove,Support,Stabilize,Preserve,Update,Avoid,Prevent,Throw,Warn,Expose - Nested detail bullets can stay explanatory when they expand on the parent bullet; do not rewrite them solely to force present or imperative tense
- Remove terminal sentence periods from bullet items because release generation appends PR/commit links after the first bullet line
- Remove terminal sentence periods from nested bullet items too, unless the punctuation is part of code, a URL, an abbreviation, a version number, or another token where removing it would be wrong
- If one bullet contains multiple sentences, split it into a shorter parent bullet plus nested bullet items
- Keep the first line concise and user-facing; use nested bullets for details or migration notes
- Remove
Review whether
scripts/changes/whats-changed.mdis needed:- Read
CHANGELOG.mdexamples orreferences/whats-changed.mdwhen uncertain - Add
scripts/changes/whats-changed.mdonly for features, future flag stabilizations, unstable flags, migration guidance, breaking bug fixes, or complex behavior that needs long-form text or examples - Do not add it for ordinary bug fixes, dependency cleanup, internal refactors, or release bullets that are already clear
- If adding it, write the body only; the release script adds
### What's Changedwhen missing
- Read
Validate:
pnpm changes:validate
pnpm changes:previewUse changes:preview to inspect the generated root release notes and confirm the PR/commit link placement, section ordering, and any manual What's Changed placement. If dependencies are missing or the command is too expensive for the context, state what was skipped.
Show full SKILL.md (138 more words)Show less
Change File Style
Single-line entries should read well with an auto-appended PR link:
Fix `href()` to stringify and URL-encode param values like `generatePath()`Use nested bullets for additional sentences:
Fix route ranking for dynamic parameters with static extension suffixes
- Identify `/:name.xml` as a dynamic segment instead of a static segment
- Preserve static route priority for paths like `/sitemap.xml`Avoid semantic commit prefixes:
Add support for nub as a package managernot:
feat: add support for nub as a package manager.What's Changed Guidance
Use scripts/changes/whats-changed.md for release-level narrative, not package-specific bullets. Good candidates include:
- A new user-facing API or feature that benefits from example code
- Stabilization or renaming of unstable APIs/flags, especially when adopters must migrate
- A stable future flag that changes behavior and needs adoption guidance
- A breaking bug fix or adapter/runtime behavior change that may require deployment checks
- A cluster of related changes whose combined effect matters more than the individual bullet list
Keep the tone direct and practical. Prefer headings under the generated ### What's Changed section:
#### Feature Name
Explain what changed, who it affects, and how to adopt it.
```ts
// Optional short example
```Do not duplicate every bullet from Minor/Patch/Unstable Changes. Let generated change files carry ordinary PR-level details.
See references/whats-changed.md for examples distilled from the existing changelog.
© remix-run, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/prepare-release-notes of remix-run/react-router.
- SKILL.md
- agents/openai.yaml
- references/whats-changed.md
Open the folder on GitHubat commit 266915e
Compare with similar skills
React Router Release Notes Prep 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 |
|---|---|---|---|---|---|---|
| React Router Release Notes Prep this skillremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Commitizencommitizen-tools/commitizen | 3.5k | — | ~839 | Automated safety check: Pass | MIT | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.3k | Automated safety check: Notes | Custom licence |
Similar skills
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
WooCommerce Git Commit
woocommerce/woocommerce
Commits pending changes with short, verb-first messages that follow WooCommerce repository conventions, splitting commits only when changes are clearly unrelated.
More from remix-run/react-router
React Router Development
remix-run/react-router
Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
React Router PR Finish Line
remix-run/react-router
Takes a blocked community pull request in React Router and adds the missing tests, change file or docs so it can merge, working on the contributor's branch.
React Router Bug Fix Workflow
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
React Router RFC Implementer
remix-run/react-router
Turns a React Router RFC discussion on GitHub into an implementation, weighing community feedback and settling open questions with you before coding.
Related
Works with
Categories
Questions about React Router Release Notes Prep
What does React Router Release Notes Prep do?
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted. changes, reads every one, and never edits generated changelogs or released notes directly. It normalizes each file: removing feat and fix semantic-commit prefixes, using imperative or present tense for the first line and top-level bullets, dropping terminal periods because release generation appends PR or commit links after the first line, and splitting multi-sentence bullets into a short parent plus nested details.
When should I use React Router Release Notes Prep?
React Router Release Notes Prep fits situations like: polishing pending change files before a React Router release; removing semantic-commit prefixes from release bullets; deciding whether a release needs a long-form What's Changed section; drafting release notes for new features or stable and unstable flags.
How do I install React Router Release Notes Prep in Claude Code?
Run `npx skills add remix-run/react-router --skill prepare-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/prepare-release-notes in remix-run/react-router) into .claude/skills/prepare-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install React Router Release Notes Prep in Codex?
Run `npx skills add remix-run/react-router --skill prepare-release-notes -a codex`. Or copy the skill folder (.agents/skills/prepare-release-notes in remix-run/react-router) into .agents/skills/prepare-release-notes in your project. Codex loads it when a task matches its description.
Can I use React Router Release Notes Prep 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 remix-run/react-router --skill prepare-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/prepare-release-notes, .gemini/skills/prepare-release-notes, .github/skills/prepare-release-notes and .opencode/skills/prepare-release-notes in your project.
What does React Router Release Notes Prep need to run?
Going by SKILL.md and its folder, React Router Release Notes Prep needs the command-line tools its instructions call (pnpm and git). Our summary lists: pnpm, with the repository's changes:validate and changes:preview scripts.
Does React Router Release Notes Prep 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 React Router Release Notes Prep 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 React Router Release Notes Prep use?
React Router Release Notes Prep 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 React Router Release Notes Prep 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 622 tokens, read only when the agent opens those files.
What are the alternatives to React Router Release Notes Prep?
Skills that share tags, products or a category with React Router Release Notes Prep: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), Commitizen (commitizen-tools/commitizen, 3.5k stars) and PR Push (icebear0828/codex-proxy, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains React Router Release Notes Prep?
remix-run (a GitHub organization) maintains it in remix-run/react-router, which has 56,597 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.
Source: remix-run/react-router on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.