agentleFS
Sign inStart free
hishamkaramhishamkaram/claude-code-router/skills/release/SKILL.md

release

Skill12 starsChanged 16 days agoMITView on GitHub

Use when preparing, validating, publishing, promoting, or recovering claude-code-router releases, including CI readiness, live E2E evidence, changelog/release-note updates, draft GitHub releases, GHCR browser images, and Homebrew promotion.

196 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

  • 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

    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

  • 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

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for version-neutral CCR release work.

    line 8
  2. Distinctive:

    Read these repo files before non-trivial release work:

    line 13
  3. Distinctive:

    When changing release mechanics, also read:

    line 23
  4. Very specific:

    Update CHANGELOG.md, docs/releases/vX.Y.Z.md, and docs/acceptance/vX.Y.Z.md.

    line 34
  5. Very specific:

    Run local gates in the order described in docs/releasing.md.

    line 38
  6. Distinctive:

    Verify the draft release assets and image, then manually promote the release workflow.

    line 43
  7. Distinctive:

    Keep macOS helper wording source-built and unsigned.

    line 45
  8. Distinctive:

    Use these assets when drafting release artifacts:

    line 57

“Common” is measured: kept by at least 6 in 10 of the 186 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

CCR Release

Use this skill for version-neutral CCR release work. Keep claims tied to evidence; a skipped live gate is not a release pass.

Required Reading

Read these repo files before non-trivial release work:

  • AGENTS.md
  • agents/_data/ai-agent-quality-contract.md
  • agents/_data/engineering-quality-gate.md
  • agents/_data/live-e2e-contract.md
  • agents/_data/router-product-invariants.md
  • agents/_data/cli-contract.md
  • agents/docs-updater.md

When changing release mechanics, also read:

  • docs/releasing.md
  • .github/workflows/release.yml
  • .goreleaser.yaml
  • scripts/publish-homebrew-formula.sh

Workflow

  1. Confirm the target version and scope. Use vX.Y.Z placeholders in reusable docs and the exact tag only in versioned release notes or acceptance files.
  2. Update CHANGELOG.md, docs/releases/vX.Y.Z.md, and docs/acceptance/vX.Y.Z.md. Do not document unimplemented behavior as shipped. Wording may describe expected release behavior only when the acceptance checklist still requires evidence before publication.
  3. Run local gates in the order described in docs/releasing.md. Read references/gates.md when deciding whether evidence is sufficient.
  4. Tag only after the acceptance file records reproducible pre-tag evidence.
  5. Let the tag workflow create a draft GitHub Release, checksums, provenance attestations, and signed GHCR browser image. Homebrew must wait.
  6. Verify the draft release assets and image, then manually promote the release workflow. Promotion publishes GitHub Release and updates Homebrew.
  7. Keep macOS helper wording source-built and unsigned; do not claim it is included in Homebrew, GoReleaser archives, signed, notarized, or hardened.
  8. Append immutable post-publication evidence to the acceptance file.

Recovery

For partial draft/public release failures, read references/recovery.md before changing tags, releases, or Homebrew. Prefer idempotent reruns over manual mutation.

Templates

Use these assets when drafting release artifacts:

  • assets/release-notes-template.md
  • assets/acceptance-template.md
  • assets/pr-body-template.md

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.

Check your setup, free