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.
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish.
Install Release
$ npx skills add cortex-tms/cortex-tms --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cortex-tms/cortex-tms 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/cortex-tms/cortex-tms.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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 cortex-tms/cortex-tms --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cortex-tms/cortex-tms release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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 cortex-tms/cortex-tms --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cortex-tms/cortex-tms release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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/cortex-tms/cortex-tms.git --path .claude/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 cortex-tms/cortex-tms --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cortex-tms/cortex-tms release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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 cortex-tms/cortex-tms 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 cortex-tms/cortex-tms --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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 cortex-tms/cortex-tms --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 cortex-tms/cortex-tms release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/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/cortex-tms/cortex-tms/tree/main/.claude/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
- 180
- Token cost
- ~398 tokens
- SKILL.md length
- 177 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish.
- Works in 4 steps: pnpm test — must pass → pnpm run lint — must have 0 errors → pnpm run build — must succeed → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Pre-release Gate, Release Steps (each requires…, Rules and Arguments
- Calls pnpm, npm and node
What it does
Release is an agent skill from cortex-tms/cortex-tms. Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
Its SKILL.md is about 400 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 Deployment. It works with pnpm. The repository describes itself as: The Universal AI-Optimized Project Boilerplate. A Tiered Memory System (TMS) designed to maximize AI agent performance. Includes an interactive CLI tool and a high-signal… The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Deployment
Example prompts
- “/release”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- pnpm test — must pass
- pnpm run lint — must have 0 errors
- pnpm run build — must succeed
- node bin/cortex-tms.js validate --strict — must pass
What it can do on your machine
Read from SKILL.md and the folder at commit 2e7c79e. 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:
pnpmnpmnodegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, npm 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
Release loads about 398 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 177 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 cortex-tms/cortex-tms at commit 2e7c79e, republished under its MIT licence (© cortex-tms). 177 words, ~398 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
- disable-model-invocation
- true
Release
Guide the user through a Cortex TMS release.
Pre-release Gate
Before starting, run the full quality gate:
pnpm test— must passpnpm run lint— must have 0 errorspnpm run build— must succeednode bin/cortex-tms.js validate --strict— must pass
If any step fails, STOP and report. Do not proceed with a broken release.
Release Steps (each requires user approval)
Bump version — show the new version number and the command. Wait for approval.
bash npm version [patch|minor|major]Sync version tags — update all version markers across docs.
bash node scripts/sync-project.jsUpdate CHANGELOG.md — draft release notes from commits since last tag. Show draft, wait for approval.
Commit release — show commit message, wait for approval.
Create git tag — show tag command, wait for approval.
bash git tag v[version]Push — show push command, wait for approval.
bash git push origin main --tagsPublish to NPM — show publish command, wait for approval.
bash npm publishCreate GitHub release — draft release notes, wait for approval.
Rules
- NEVER skip a step
- NEVER proceed without explicit user approval at each gate
- If something fails mid-release, stop and explain how to recover
Arguments
$ARGUMENTS
© cortex-tms, 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 .claude/skills/release of cortex-tms/cortex-tms.
Open the folder on GitHubat commit 2e7c79e
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 skillcortex-tms/cortex-tms | 180 | — | ~398 | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Release Notespnpm/pnpm | 37k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| EverOS Release WorkflowEverMind-AI/EverOS | 13k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Release Notes
pnpm/pnpm
Curate a pending release page - merging entries that describe one change, dropping notes for defects that never shipped, ordering by importance, and checking the version the intents ask for.
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.
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
Release
ngrok/ngrok-operator
Automates the ngrok-operator release process: gathers PR data, classifies changes by component (container, Helm chart, CRDs chart), generates changelogs, updates version files, and prepares the…
More from cortex-tms/cortex-tms
Plan
cortex-tms/cortex-tms
Research the codebase and create an implementation plan following Propose/Justify/Recommend.
Implement
cortex-tms/cortex-tms
Implement an approved plan. An agent skill from cortex-tms/cortex-tms.
New Command
cortex-tms/cortex-tms
Scaffold a new CLI command for Cortex TMS following the existing codebase patterns.
Sync
cortex-tms/cortex-tms
Synchronize task files and source-of-truth documents. An agent skill from cortex-tms/cortex-tms.
Validate
cortex-tms/cortex-tms
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
Related
Works with
Categories
Questions about Release
What does Release do?
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Release is an agent skill from cortex-tms/cortex-tms. Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish.
When should I use Release?
Release fits situations like: tasks that involve Changelog and release notes; tasks that involve Deployment.
How do I install Release in Claude Code?
Run `npx skills add cortex-tms/cortex-tms --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in cortex-tms/cortex-tms) 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 cortex-tms/cortex-tms --skill release -a codex`. Or copy the skill folder (.claude/skills/release in cortex-tms/cortex-tms) 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 cortex-tms/cortex-tms --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 (pnpm, npm, node and git).
Does Release access the network?
SKILL.md contains no URLs. Its commands use npm and git, 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 398 tokens (SKILL.md is roughly 1.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), Release Notes (pnpm/pnpm, 37k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Cline Desktop App Release (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
cortex-tms (a GitHub organization) maintains it in cortex-tms/cortex-tms, which has 180 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: cortex-tms/cortex-tms on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.