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.
Execute a Kobato release. An agent skill from syhily/kobato.
Install Release
$ npx skills add syhily/kobato --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install syhily/kobato release --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/syhily/kobato.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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/syhily/kobato/tree/main/.agents/skills/releaseType 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 syhily/kobato --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install syhily/kobato release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syhily/kobato.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release .agents/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 syhily/kobato --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install syhily/kobato release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syhily/kobato.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release .cursor/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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/syhily/kobato.git --path .agents/skills/release--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 syhily/kobato --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install syhily/kobato release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syhily/kobato.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release .gemini/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 syhily/kobato releaseInstalls 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 syhily/kobato --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/syhily/kobato.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release .github/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 syhily/kobato --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install syhily/kobato release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syhily/kobato.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release .opencode/skills/release && 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" agent skill from https://github.com/syhily/kobato/tree/main/.agents/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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- GitHub stars
- 114
- Token cost
- ~1.2k tokens
- SKILL.md length
- 578 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute a Kobato release. An agent skill from syhily/kobato.
- Works in 7 steps: Validate arguments → Validate preconditions → Analyze commits → …
- The user runs /release <version <next-version
- SKILL.md covers Step 0: Validate arguments, Step 1: Validate preconditions, Step 2: Analyze commits and Step 3: Study the release…, plus 4 more sections
- Calls git, node and gh
What it does
Release is an agent skill from syhily/kobato. Execute a Kobato release. Use when the user runs /release <version <next-version or asks to release the project. The first argument is the version to release, the second is the next development version.
Its SKILL.md is about 1.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. It works with React Router. The repository describes itself as: An open source blog system for the writers. The licence is MIT.
When your agent uses it
- The user runs /release <version <next-version
- Asks to release the project
Example prompts
- “/release”
Requirements
- Docker
Workflow steps
7 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 534dd92. 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:
gitnodegh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Release loads about 1.2k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 578 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 syhily/kobato at commit 534dd92, republished under its MIT licence (© syhily). 578 words, ~1,152 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Execute a Kobato release. Use when the user runs `/release <version> <next-version>` or asks to release the project. The first argument is the version to release, the second is the next development version.
- arguments
- version, next_version
Release
Execute a Kobato release. The user provides two arguments:
$version— the version to release (e.g.6.3.0).$next_version— the next development version on develop (e.g.6.4.0-dev).
The entire release lifecycle runs automatically: analyze commits, draft notes, bump version, push to develop, fast-forward merge to main, tag and create the GitHub release, switch back to develop, prepare the next cycle, and push.
Step 0: Validate arguments
Both $version and $next_version must be present and match X.Y.Z or X.Y.Z-prerelease (e.g. 6.3.0, 6.3.0-beta.1, 6.4.0-dev). If either is missing or malformed, stop and ask the user for the correct value.
Step 1: Validate preconditions
- Run
git branch --show-current— must be ondevelop. - Run
git status --porcelain— working tree must be clean. If dirty, stop and tell the user to commit or stash. - Run
node scripts/release.ts since-last— note the last released tag.
Step 2: Analyze commits
Run git log <last-tag>..HEAD --format="%h %s" to get all commits since the last release.
If there are zero commits, tell the user there's nothing to release and stop.
Step 3: Study the release notes style
Run gh release view <last-tag> to read the most recent release notes body. This is your primary style reference.
Also read the second-most-recent release for additional context: run gh release view <tag-before-that>.
Internalize these style rules:
- Title:
## Kobato X.Y.Z(h2, with "Kobato" prefix) - Lead paragraph: 1–2 sentences summarizing the release themes, with bolded feature names inline
- Sections: Use
###headers with emoji prefixes —### ✨ New Features,### 🛡️ Security Hardening,### 🏗️ Architecture & Refactoring,### 🔧 Build & Dependencies,### 🐛 Fixes. Only include sections that have entries. Add extra sections (e.g.,### 🎨 UI Redesign,### 🎵 Music Player) if a thematic grouping makes sense. - Sub-headers:
**Bold Title Case**to group related items within a section. - Bullets: Each change is a single
-bullet, concise and technical. Describe what changed and often why. Use sentence case. - Language: English. Technical, precise, no first person.
- Emojis: Only as section header prefixes, never inline.
- Footer:
**Full Changelog**: [prev...current](https://github.com/syhily/kobato/compare/PREV...CURRENT)— a clickable markdown link
Show full SKILL.md (256 more words)Show less
Step 4: Draft release notes
Based on the commit analysis and the established style, draft the release notes. Group related commits under thematic sub-headers. Expand terse commit messages into descriptive bullets — the reader should understand what changed and why without reading the code.
For commits that are purely internal (e.g., refactor: move X to Y), collapse related ones into a single bullet rather than listing each individually.
Show the draft to the user and ask for approval or edits. Wait for their response before proceeding.
Step 5: Bump version
After the user approves the release notes, run:
node scripts/release.ts bump $versionVerify the commit was created:
- Run
git log -1 --format="%h %s"— should showbuild: release $version.
Step 6: Publish
Now execute the full publish sequence automatically:
git push origin developgit checkout maingit merge develop --ff-only— fast-forward merge. If this fails (diverged histories), stop and tell the user to resolve manually.git push origin main- Write the approved release notes to
/tmp/kobato-release-notes.md node scripts/release.ts tag --notes-file /tmp/kobato-release-notes.md— creates git tag and GitHub releasegit checkout developgit merge main --ff-only— sync main back to developnode scripts/release.ts prepare-next $next_version— sets develop to$next_versionand docker-compose tolatestgit push origin develop
After all steps complete, report the release URL and the new development version.
Recovery (when the full flow is interrupted)
- Tag/publish only: run
node scripts/release.ts tag --notes-file /tmp/kobato-release-notes.mdfrommainwith the release commit already present. - Prepare next cycle only: run
node scripts/release.ts prepare-next <next_version>fromdevelop.
© syhily, MIT. 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 .agents/skills/release of syhily/kobato.
Open the folder on GitHubat commit 534dd92
Compare with similar skills
Release 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 this skillsyhily/kobato | 114 | — | ~1.2k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| React Router PR Finish Lineremix-run/react-router | 57k | — | ~1.4k | Automated safety check: Pass | MIT | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| React Router Framework Modecurvenote/curvenote | 170 | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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 Framework Mode
curvenote/curvenote
Build full-stack React applications using React Router's framework mode.
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.
More from syhily/kobato
Vercel Geist Design System
syhily/kobato
Community skill for applying the Geist design system to Vercel-inspired rendered frontend UI across React/Next.js/Vite/Astro/Svelte/Vue/HTML/CSS, Tailwind, shadcn, and Radix.
Related
Works with
Categories
Questions about Release
What does Release do?
Execute a Kobato release. An agent skill from syhily/kobato. Release is an agent skill from syhily/kobato. Execute a Kobato release.
When should I use Release?
Release fits situations like: the user runs /release <version <next-version; asks to release the project.
How do I install Release in Claude Code?
Run `npx skills add syhily/kobato --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in syhily/kobato) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add syhily/kobato --skill release -a codex`. Or copy the skill folder (.agents/skills/release in syhily/kobato) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release 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 syhily/kobato --skill release -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, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, node and gh). Our summary lists: Docker.
Does Release access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release 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 use?
Release 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 Release use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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?
Skills that share tags, products or a category with Release: React Router Release Notes Prep (remix-run/react-router, 57k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), React Router PR Finish Line (remix-run/react-router, 57k stars) and React Router Bug Fix Workflow (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?
syhily (a GitHub user) maintains it in syhily/kobato, which has 114 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 30, 2026.
Source: syhily/kobato on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.