agentsclimarketplace
Sign in

Prepare release

Skill brandtam/skills/skills/prepare-release

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.From its SKILL.md

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 file declares

Copied from the file, not written here

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/

Keep looking

Skills are one crate of 325,949. 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.