agentsclimarketplace

Release prep

Skill bakerstreetco/skills/release-prep

Reusable agent skills for real repository work: review, implementation, release, documentation, and project hygiene.

Install
npx -y skills add bakerstreetco/skills --skill release-prep

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 repository for release by checking versioning, changelog, tests, build artifacts, tags, package metadata, and release notes. Use when asked to cut a release, prepare release notes, publish a package, tag a version, or verify release readiness.

SKILL.md

1.7 KB, as published. Nobody here has run it

Release Prep

Use this skill to make releases repeatable and evidence-backed. Do not tag, push, publish, or create a hosted release until repository identity, remote, and release target are verified.

Workflow

  1. Identify the current version, package ecosystem, release branch, remote, and release conventions.
  2. Inspect recent commits, changelog, previous tags, existing release notes, package metadata, and CI status.
  3. Determine required release files: version bumps, changelog entries, generated docs, lockfiles, manifests, distribution artifacts, or migration notes.
  4. Run the repository's release gates: tests, lint, typecheck, build, package validation, smoke tests, and docs generation when applicable.
  5. Prepare release notes from real commits and PRs. Group by user impact, fixes, breaking changes, and internal changes.
  6. Create tags, hosted releases, or package uploads only when explicitly requested and after identity verification.

Checks

  • Version numbers are consistent across manifests and docs.
  • Changelog matches actual changes.
  • Build artifacts are regenerated only when the repo tracks them.
  • Breaking changes and migration steps are documented.
  • Package metadata links, license, README, and files included in the package are correct.
  • Release commands are current and tested where possible.

Output

Report release readiness, files changed, verification commands, proposed release notes, and any blockers before publish.

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.