Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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.
Type 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.
skills CLI
$ npx skills add seasonedcc/remix-forms --skill release -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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.
skills CLI
$ npx skills add seasonedcc/remix-forms --skill release -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add seasonedcc/remix-forms --skill release -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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.
GitHub CLI
$ gh skill install seasonedcc/remix-forms release
Installs 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).
skills CLI
$ npx skills add seasonedcc/remix-forms --skill release -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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.
skills CLI
$ npx skills add seasonedcc/remix-forms --skill release -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "release" agent skill from https://github.com/seasonedcc/remix-forms/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
514
Token cost
~1.3k tokens
SKILL.md length
547 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT
At a glance
Release a new version of the remix-forms npm package. An agent skill from seasonedcc/remix-forms.
Works in 8 steps: Verify on main branch → Determine the next version → Bump version in… → …
The user mentions releasing
Calls pnpm, git and gh
Cutting a release
What it does
Release is an agent skill from seasonedcc/remix-forms. Release a new version of the remix-forms npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
Its SKILL.md is about 1.3k 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 npm, GitHub, React Router and pnpm. The repository describes itself as: Full-stack forms for React Router. The licence is MIT.
When your agent uses it
The user mentions releasing
Cutting a release
Shipping a new version
Example prompts
“/release”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7030d30. 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:
pnpm
git
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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.3k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 547 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~54
When it runs· the whole SKILL.md, loaded when a task matches
~1.3k
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.
Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Release a new version of the remix-forms npm package. Bump version, build, publish, and create a GitHub release. Use when the user mentions releasing, publishing, cutting a release, or shipping a new version.
metadata.internal
true
Release
Automate the release workflow for the remix-forms npm package.
Instructions
0. Verify on main branch
Before doing anything else, confirm the working tree is on main and up to date:
bash
git branch --show-current
If not on main, switch and pull:
bash
git checkout main && git pull
Never start a release from a feature branch. Version bumps, commits, and tags must land on main.
1. Determine the next version
Find the latest git tag:
bash
git tag --list 'v*' --sort=-version:refname | head -1
Read the current version from packages/remix-forms/package.json.
minor for new features that are backwards-compatible
major for breaking changes
prerelease (e.g. 5.0.0-alpha.4) when the user asks for an alpha/beta/rc release — increment the prerelease suffix
Bump the patch version unless the user specifies otherwise.
2. Bump version in packages/remix-forms/package.json
Edit packages/remix-forms/package.json to set the new version number.
3. Run pnpm install
bash
pnpm install
This updates the lockfile with the new version.
4. Run checks
bash
pnpm run lint-fix && pnpm run lint && pnpm run tsc && pnpm run test && pnpm run build
All must pass before proceeding.
5. Commit and push
Commit packages/remix-forms/package.json and pnpm-lock.yaml with message v<new-version>. Push to main.
6. Ask the user to publish
For stable releases, tell the user to run:
bash
cd packages/remix-forms && pnpm publish
For prerelease versions (alpha/beta/rc), tell the user to run:
bash
cd packages/remix-forms && pnpm publish --tag alpha
The --tag alpha flag prevents npm from marking the prerelease as latest.
Do not run pnpm publish yourself — it requires an OTP. Wait for the user to confirm they've published before continuing.
7. Create the GitHub release
Once the user confirms the publish, write release notes by thoroughly analyzing the changes.
Show full SKILL.md (299 more words)Show less
Analyze changes in depth
Do not just list PRs. Study the actual changes to understand what they mean for users:
Check dependency changes first — diff packages/remix-forms/package.json for new/removed/changed peerDependencies and dependencies. Peer dependency bumps are the highest-impact breaking changes because they gate who can install the package at all (e.g., raising the React peer dep from >=16.8 to >=18 blocks every user on React 17 or below). Flag these immediately.
Check the public API diff — look at changes to packages/remix-forms/src/index.ts for added/removed exports.
Filter to package-relevant changes — use git log <last-tag>..HEAD --oneline -- packages/remix-forms/ to identify commits that actually affect the published package (vs website-only changes).
List merged PRs between the two tags:
bash
gh pr list --search "is:merged merged:>=<last-tag-date>" --json number,title,author --limit 100
Read every PR's description — PR bodies contain author-written summaries, migration instructions, and context that titles and diffs alone don't provide. Read each one:
Run these in parallel (all PR reads in a single message) for efficiency.
Read the changed source code when a PR description is missing or unclear — don't assume what a change does from the title alone.
Write release notes
Use the following structure. Include only the sections that apply:
## Breaking Changes — narrative subsections explaining each breaking change, what it replaces, and what users need to do. Order by impact: dependency requirement changes first (peer dep bumps affect every user at install time), then behavioral or API changes. Include code examples showing before/after when helpful.
## New Features — bullet points with bold title, PR number in parens, and a one-line description drawn from the PR body.
## Bug Fixes — bullet points with PR number and linked issue closes (e.g. "Closes #123").
## What's Changed — full PR list with author links, formatted as:
* <title> by @<author> in https://github.com/seasonedcc/remix-forms/pull/<number>
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.
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…
Cut and publish a new tellux release — bump version, curate a changelog summary from recent commits, pause for the user to manually pnpm publish (browser 2FA), then push the tag and create the…
Fix a PR that is failing due to security or vulnerability issues — npm/pnpm/yarn/bun audit failures, CVE alerts, Dependabot merge conflicts, Snyk failures, or GitHub security advisory blocks.
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.
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
Release a new version of the remix-forms npm package. An agent skill from seasonedcc/remix-forms. Release is an agent skill from seasonedcc/remix-forms. Release a new version of the remix-forms npm package.
When should I use Release?
Release fits situations like: the user mentions releasing; cutting a release; shipping a new version.
How do I install Release in Claude Code?
Run `npx skills add seasonedcc/remix-forms --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in seasonedcc/remix-forms) 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 seasonedcc/remix-forms --skill release -a codex`. Or copy the skill folder (.claude/skills/release in seasonedcc/remix-forms) 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 seasonedcc/remix-forms --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, git and gh).
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.3k tokens (SKILL.md is roughly 5.2k 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: Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars), Release (cyanfish-x/tellux, 207 stars), Fix Security PR (unional/typescript-blackbook, 133 stars) and Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
seasonedcc (a GitHub organization) maintains it in seasonedcc/remix-forms, which has 514 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on April 15, 2026.
Source: seasonedcc/remix-forms on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.