agentsclimarketplace

Prepare release

Skill brandtam/skills/skills/prepare-release

Agent skills that follow the open Agent Skills spec — usable by Claude Code, Codex, and any compliant agent.

Install
npx -y skills add brandtam/skills --skill prepare-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Prepare a release from pending changesets by previewing the next version, generating the changelog, archiving consumed notes, and preparing tag or GitHub Release steps. Use when the user asks to prepare, cut, publish, or generate a release from pending changesets.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 383 tokens by cl100k_base, as published. Nobody here has run it

Prepare Release

Use this skill when the user wants to turn pending changesets into a release.

First Checks

  1. Read repo instructions such as AGENTS.md, CLAUDE.md, and release docs.
  2. Confirm the repo already has a changeset workflow and release command.
  3. Confirm pending .changeset/*.md files exist.
  4. Inspect the current version, changelog, branch, working tree, tags, CI expectations, and deployment model.

If the workflow is missing, stop and say the repo does not have changeset release tooling installed. Do not scaffold it from this skill.

If there are no pending changesets, stop and report that there is nothing to release.

Release Workflow

  1. Run the repo's dry-run or status command first.
  2. Summarize the pending changesets, next version, and generated changelog preview.
  3. Run required validation, usually tests, lint, build, and relevant browser checks.
  4. Run the mutating version/changelog/archive command only when the user has asked to proceed.
  5. Review generated files, especially CHANGELOG.md.
  6. Prepare the release commit, tag, and GitHub Release notes.

Boundaries

  • Do not create missing changeset tooling.
  • Do not invent release notes without pending changesets.
  • Do not delete consumed changesets; they should move to .changeset/released/<version>/.
  • Do not create, move, or push tags without explicit approval.
  • Do not publish a GitHub Release without explicit approval.
  • Treat published tags as immutable. Ship a follow-up patch rather than rewriting a release tag.

References

  • For the command sequence and file behavior, read references/release-workflow.md.
  • For GitHub Release expectations, read references/github-releases.md.
  • For prompt and response examples, read references/examples.md.

What ships with it: 3 files

3.0 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most ship operate skills give in 383 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • confirm changeset workflow and release command exist
  • confirm pending changeset files exist
  • run repository dry-run or status command
  • summarize pending changesets and next version
  • run version and changelog commands only after approval
  • review generated changelog files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.