Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Release Automation with Changesets and release-please

    1

    Automate semver, changelogs, tags, GitHub Releases and npm/PyPI publishing with trusted publishing (OIDC) and a dry run first. AUTOMATED / SEMI-MANUAL / BROKEN.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Release Automation with Changesets and release-please

    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

    PathPurpose
    .changeset/config.jsonindependent versions, @acme/docs and @acme/playground marked private, internal deps bumped as patch
    .github/workflows/release.ymlon push to main: build, then changesets/action opens a "Version Packages" PR or publishes once it is merged
    .github/workflows/changeset-check.ymlPRs touching packages/** need a changeset or the no-changeset label
    RELEASING.mdhow to add a changeset, pre-releases (changeset pre enter next), rollback (deprecate + fix release)
    packages/*/package.jsonadded 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-run on each package: dist/ only. Removed src/__fixtures__ (1.8 MB) from @acme/icons by adding a files field.
    • Not run: a real publish (as requested).

    You must do (not done by me)

    1. On npmjs.com, add a trusted publisher for each of the 4 packages: this repo, workflow release.yml.
    2. Revoke the shared automation token after the first successful release.
    3. Optional: add a release environment with required reviewers and point the job at it.
    4. Tag the existing 2.4.1 commit for @acme/icons so history matches npm (command in RELEASING.md).

    Next release walkthrough

    1. Open a PR and run pnpm changeset to describe the change.
    2. Merge it. The bot opens or updates "Version Packages".
    3. Review the versions and changelog in that PR, then merge.
    4. The workflow publishes with provenance and creates GitHub Releases.
    so history matches npm (command in RELEASING.md

    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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    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

    Requires

    Git
    GitHub repository
    GitHub Actions
    Node.js or your language toolchain
    npm or PyPI account
    semantic-release
    Node.js
    changeset

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    Any agent that supports the SKILL.md standard, including Claude Code, Codex CLI, Cursor, VS Code Copilot and Gemini CLI.

    SKILL.md with the full setup procedure, verdict rules and report format; a tool-choice guide comparing Changesets, release-please and semantic-release; and GitHub Actions templates for each, plus a PR-title check.

    Not without your explicit approval. It sets everything up and runs dry runs that show the computed versions and the exact package contents. Real publishing only happens when you merge the release PR or approve a release.

    No. It prefers trusted publishing (OIDC) so CI gets short-lived credentials. You configure the trusted publisher in the registry's settings. If a token is still required, you add it to CI secrets yourself; it is never pasted into chat.

    Changesets for JS/TS monorepos or teams without commit conventions, release-please for non-JS or mixed-language repos, and semantic-release for single packages that ship on every merge. It explains the choice in the report.

    Templates target GitHub Actions; for GitLab CI or others it adapts the same steps but the templates need translating. Registry settings such as trusted publishers must be changed by you in the registry's web UI.

    New in DevOps & Cloud