changesets

Automate multi-package versioning and changelog management in monorepos.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-vite-react --skill changesets-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changesets
Source: https://github.com/pohlai88/afenda-vite-react/tree/main/.agents/skills/changesets
Command: npx skills add https://github.com/pohlai88/afenda-vite-react --skill changesets-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually coordinating version bumps and changelogs across many packages in a monorepo is error-prone and time-consuming.

Core Features & Use Cases

  • Consolidated versioning across packages with independent version numbers
  • Automated changelog generation and publish workflows for multi-package repos
  • Use cases include coordinated releases, CI validation, and dependency updates across a Turborepo/pnpm workspace

Quick Start

Run changesets add and version to declare and apply a release across all affected packages.

Frequently Asked Questions about changesets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-package versioning and changelogs in a monorepo?

You can automate multi-package versioning by running changesets add and version to declare and apply releases, which coordinates independent version bumps and generates changelogs across all affected packages.

What is the best way to coordinate independent version numbers across packages in a pnpm workspace?

The best way to coordinate independent version numbers is using changesets to consolidate versioning, which automatically drives version bumps and dependency updates across packages in your pnpm workspace.

Does changesets work with Turborepo for multi-package release workflows?

Yes, changesets works with Turborepo to support coordinated releases, CI validation, and dependency updates across multi-package repos, consolidating versioning and automating changelog generation workflows.

Why do I need a .changeset/config.json file to manage semver bumps?

You need the .changeset/config.json file because it provides the required Changesets tooling configuration to drive per-package version bumps, dependency updates, and automated changelog generation.

How do I publish multiple packages to npm from a monorepo after a version bump?

You publish multiple packages to npm by running the changesets workflow, which coordinates the release cycle and automates the publishing process across all affected packages after applying version bumps.