agentleFS
jayminwestjayminwest/warren/.agents/skills/release/SKILL.md

release

Skill519 starsChanged 3 months agoMITView on GitHub

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

  • Commits and pushes

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No open PRs about to auto-merge into the release commit: gh pr list --state open.

    line 19
  2. Very specific:

    Run bun run version:bump <major|minor|patch>.

    line 51
  3. Distinctive:

    Update the Seam status table for any seam this release changed.

    line 76
  4. Distinctive:

    Commit the release changes (version sites, CHANGELOG, ROADMAP, docs).

    line 100
  5. Very specific:

    Verify the release was promoted out of draft: gh release view vX.Y.Z shows it final and --latest.

    line 110
  6. Distinctive:

    If any job failed, say so plainly and stop — a draft release with no image is the designed failure state, not a partial success.

    line 115

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.