- Home
- Skills
- DevOps & Cloud
- Release Automation with Changesets and release-please
Works with the AI Agents you already use
Release Automation with Changesets and release-please
Automate semver, changelogs, tags, GitHub Releases and npm/PyPI publishing with trusted publishing (OIDC) and a dry run first. AUTOMATED / SEMI-MANUAL / BROKEN.
$5
Release Automation with Changesets and release-please
Example session with this skill installed
We maintain 4 npm packages in a pnpm monorepo. Releases are manual: someone bumps versions, writes the changelog, and runs npm publish locally with a shared token. Automate it properly. Dry run only, don't publish anything.
- Read your context and instructions
- Compiled the release automation
Release setup: ui-kit monorepo (2026-10-19)
Verdict: AUTOMATED (was BROKEN: shared long-lived npm token; @acme/icons on npm at 2.4.1 but no matching git tag)
Choice: Changesets, because it is a pnpm monorepo with 4 published packages and commit messages are not consistently conventional (38 of the last 100 match).
Files added / changed
| Path | Purpose |
|---|---|
.changeset/config.json | independent versions, @acme/docs and @acme/playground marked private, internal deps bumped as patch |
.github/workflows/release.yml | on push to main: build, then changesets/action opens a "Version Packages" PR or publishes once it is merged |
.github/workflows/changeset-check.yml | PRs touching packages/** need a changeset or the no-changeset label |
RELEASING.md | how to add a changeset, pre-releases (changeset pre enter next), rollback (deprecate + fix release) |
packages/*/package.json | added files and publishConfig.access: public; repository field so provenance can link to source |
Permissions: workflow default contents: read. The release job only gets contents: write, pull-requests: write, id-token: write.
Dry run (measured)
changeset status --verbose: 3 pending changesets- Computed next versions: @acme/core 3.2.0 -> 3.3.0 (minor), @acme/react 3.2.0 -> 3.2.1 (patch, dependency bump), @acme/icons 2.4.1 -> 2.5.0
npm pack --dry-runon each package: dist/ only. Removedsrc/__fixtures__(1.8 MB) from @acme/icons by adding afilesfield.- Not run: a real publish (as requested).
You must do (not done by me)
- On npmjs.com, add a trusted publisher for each of the 4 packages: this repo, workflow
release.yml. - Revoke the shared automation token after the first successful release.
- Optional: add a
releaseenvironment with required reviewers and point the job at it. - Tag the existing 2.4.1 commit for @acme/icons so history matches npm (command in RELEASING.md).
Next release walkthrough
- Open a PR and run
pnpm changesetto describe the change. - Merge it. The bot opens or updates "Version Packages".
- Review the versions and changelog in that PR, then merge.
- The workflow publishes with provenance and creates GitHub Releases.
Connects securely to your tools. The creator never sees your data.
About this skill
Someone bumps the version by hand, forgets the changelog, tags the wrong commit, and publishes from their laptop with a long-lived npm token that three people share. Or the release tool was set up once, half works, and nobody trusts it. Releases should be boring.
This skill gives your coding agent a safe procedure to set up or repair automated releases, plus a tool-choice guide and ready-to-adapt GitHub Actions templates. It:
- Assesses the current state: registries (npm, PyPI, crates.io, Go tags, Docker, GitHub Releases), single package or monorepo, where versions live, whether they match the latest tag, commit message style, merge strategy, and where tokens are used
- Picks one tool with a stated reason: Changesets (JS/TS monorepos, human-written change notes), release-please (any language, release PR from Conventional Commits) or semantic-release (zero-touch releases for a single package)
- Adds the config and a least-privilege workflow: read-only by default, write and id-token permissions only on the job that needs them
- Uses trusted publishing (OIDC) for npm and PyPI instead of long-lived tokens, with provenance where supported and an optional protected release environment for a human approval gate
- Handles monorepo details: fixed vs independent versions, private packages, internal dependency ranges, pre-release channels
- Adds commit or PR-title enforcement when a commit-driven tool needs it
- Runs a dry run and checks exactly what would be published (npm pack --dry-run, uv build + twine check) before anything ships
- Writes a short RELEASING.md, including how to roll back safely
- Gives a verdict: AUTOMATED, SEMI-MANUAL or BROKEN, with the starting state and the state after changes
For maintainers of libraries, SDKs, CLIs, internal packages and apps that ship versions.
Safety and honesty: it never publishes, tags, pushes or creates a release without your explicit approval, never asks you to paste tokens into chat, and continues from your real version history instead of resetting it. It reports only dry runs as done unless you approved a real release, and says so when a registry feature cannot be confirmed for your account.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
GitHub Actions templates included; other CI systems need the same steps translated. Registry settings (trusted publishers, token revocation, environments) must be changed by you. It runs dry runs only unless you approve a real release.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 28 days ago
- Accounts
- npmorPyPI account
- Software
GitGitHub repositoryGitHub Actions
Node.js
oryour language toolchainsemantic-releasechangeset
Node.js runs Changesets or semantic-release. The npm or PyPI account needs access to the package settings.