New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by jayminwest in jayminwest/warren

Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add jayminwest/warren --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jayminwest/warren release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jayminwest/warren.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release
GitHub stars
476
Token cost
~1.3k tokens
SKILL.md length
719 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.

  • Works in 10 steps: Pre-flight → Tracker audits (two parallel subagents) → Review changes since the last tag → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers 1. Pre-flight, 2. Tracker audits (two…, 3. Review changes since the… and 4. Bump the version, plus 6 more sections
  • Calls git, gh and bun

What it does

Release is an agent skill from jayminwest/warren. Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.

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, covering Changelog and release notes. It works with Git. The repository describes itself as: Run coding agents like infrastructure, not terminal sessions. Warren manages isolation, lifecycle, spend, recovery, and Git delivery on compute you control. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/release”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Pre-flight
  2. Tracker audits (two parallel subagents)
  3. Review changes since the last tag
  4. Bump the version
  5. Curate the CHANGELOG — this is a fatal release gate
  6. Update ROADMAP.md
  7. Doc pass
  8. Run the gates locally
  9. Commit and push
  10. Watch the pipeline and verify

What it can do on your machine

Read from SKILL.md and the folder at commit 5276209. 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:

    • git
    • gh
    • bun
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh and npm, 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 45 tokens; SKILL.md has 719 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
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.

SKILL.md

The full file from jayminwest/warren at commit 5276209, republished under its MIT licence (© jayminwest). 719 words, ~1,273 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.

Release

Prepare a new warren release, push it, and verify the pipeline shipped it. The release does not exist when the commit lands — it exists when the Release workflow's five-job chain finishes: gates → tag → draft release → ghcr image + GKE deploy → npm publish → promote draft to final → Discord announce. This command runs everything up to the push, then watches that chain to the end.

1. Pre-flight

  • Working tree is clean, on main, up to date with origin (git status, git pull).
  • No open PRs about to auto-merge into the release commit: gh pr list --state open. If one is close to merging, either wait for it or release without it deliberately — never race it.
  • Find the last release tag: git describe --tags --abbrev=0.

2. Tracker audits (two parallel subagents)

Spawn both subagents in a single message so they run concurrently. Neither pushes — all commits ride out with the single push in step 9.

  • Seeds audit — a subagent that invokes the seeds-issue-audit skill and follows it exactly: auto-close only HIGH-confidence issues with citable evidence, run sd sync after closing, report borderline cases, never push. Have it return its two tables (auto-closed / borderline).
  • GitHub issue sweep — a subagent that lists open GitHub issues (gh issue list --state open) and verifies each against HEAD. Same discipline as the seeds audit: close an issue only when the fix is verifiably on main (name the commit or merged PR in the closing comment, gh issue close <n> --comment "..."); anything uncertain goes in a borderline table, untouched. Staleness alone never closes anything.

Hold both reports — the borderline tables go in the final summary (step 10), and confirmed-done plans feed the ROADMAP update (step 6).

3. Review changes since the last tag

  • git log <tag>..HEAD --oneline and git diff <tag>..HEAD --stat.
  • Determine the version bump level. Always use patch unless the user explicitly requests minor or major.

4. Bump the version

Run bun run version:bump <major|minor|patch>. It rewrites all four version sites (package.json, src/index.ts, docs/openapi.yaml via gen:openapi, and the README ## Status line) and drafts an [Unreleased] CHANGELOG block from the commit log.

5. Curate the CHANGELOG — this is a fatal release gate

Rework the drafted block by hand: regroup entries under ### Added / ### Changed / ### Fixed, rename the heading to ## [X.Y.Z] - <today's date>, and delete the <!-- version-bump:draft --> markers.

The Release workflow fails the release if CHANGELOG.md has no non-empty ## [X.Y.Z] section — notes are never auto-generated. Write for the reader of the GitHub release and the Discord announcement, not for the git log.

Show full SKILL.md (308 more words)Show less

6. Update ROADMAP.md

Reconcile the roadmap with what this release ships, following its own rules (shipped items shrink to one table row; no design sketches):

  • Move finished campaigns/plans out of Now — in flight into the Shipped table — one row, the new version number, a pointer to the design record. Use the seeds audit's confirmed-done plans as the input.
  • Update the Seam status table for any seam this release changed.
  • Re-order Next if the shipped work unblocked or promoted an item.

7. Doc pass

The gates already hold generated docs in place (gen:docs:check, gen:openapi:check, gen:cli-ref:check, check:agents), so this pass is prose only:

  • CLAUDE.md (a symlink to AGENTS.md) if structure or command counts changed.
  • README.md if the pitch, stats, or install instructions drifted.

8. Run the gates locally

bash
bun run check:all

The Release workflow runs this same manifest first and a failure kills the release with the version already bumped on main. Catch it here instead.

9. Commit and push

Commit the release changes (version sites, CHANGELOG, ROADMAP, docs). This is the single push point: the tracker-audit commits from step 2 ride out with it. Then git push. The push triggers the Release workflow (it fires on main pushes touching package.json / CHANGELOG.md).

10. Watch the pipeline and verify

  • Watch the Release workflow to completion: gh run list --workflow=release.yml --limit 1, then gh run watch <run-id>.
  • Verify the release was promoted out of draft: gh release view vX.Y.Z shows it final and --latest. By the pipeline's ordering guarantee, a promoted release proves the ghcr image and the npm package already exist; spot-check npm anyway: npm view @os-eco/warren-cli@X.Y.Z version.
  • If any job failed, say so plainly and stop — a draft release with no image is the designed failure state, not a partial success.

Finish with a summary: version, highlights, links (release URL, workflow run), and the two borderline tables from step 2 for human review.

© jayminwest, 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 jayminwest/warren.

Open the folder on GitHubat commit 5276209

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skilljayminwest/warren476—~1.3kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • 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.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • 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.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • 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.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jayminwest/warren

  • Os Eco Dep Sync

    jayminwest/warren

    Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR.

    476 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Good First Issue Batch

    jayminwest/warren

    File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor.

    476 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Seeds Issue Audit

    jayminwest/warren

    Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases.

    476 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Warren Dogfood Pipeline

    jayminwest/warren

    Full prioritize → dispatch → shepherd → track pipeline against the live warren instance.

    476 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts. Release is an agent skill from jayminwest/warren. Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.

When should I use Release?

Release fits situations like: tasks that involve Changelog and release notes.

How do I install Release in Claude Code?

Run `npx skills add jayminwest/warren --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in jayminwest/warren) 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 jayminwest/warren --skill release -a codex`. Or copy the skill folder (.agents/skills/release in jayminwest/warren) 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 jayminwest/warren --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, gh, bun and npm).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, gh and npm, 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.1k 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), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

jayminwest (a GitHub user) maintains it in jayminwest/warren, which has 476 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

Source: jayminwest/warren on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.