skills.rest
OpenSaasAU
OpenSaasAUOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-changeset

Generate changeset files for package changes in a monorepo.

2|Updated Oct 17, 2025
Search Tags:#git#versioning#monorepo#package#pull-request#changeset
One-click install
npx skills add https://github.com/OpenSaasAU/stack --skill pr-changeset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-changeset
Source: https://github.com/OpenSaasAU/stack/tree/main/.claude/skills/pr-changeset
Command: npx skills add https://github.com/OpenSaasAU/stack --skill pr-changeset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures you create proper changeset files whenever you modify code in any package under packages/*. It standardizes version bumps (patch for bug fixes, minor for features, major only when requested) and prepares release notes before commits and PRs.

Core Features & Use Cases

  • Automated changeset creation: Generate a .changeset file for package changes in a PR or commit.
  • Semantic versioning guidance: Choose patch, minor, or major based on the change description.
  • Release hygiene: Keeps changelog and release notes in sync with repository changes; list affected packages in a single changeset file.

Quick Start

When you modify code in any package, describe the change in a short sentence (e.g., "Fix validation error in text field when value is null"). A .changeset/*.md file will be created. Review and adjust the description if needed, then commit both your changes and the changeset file.

Frequently Asked Questions about pr-changeset

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

FAQPage Schema
How do I create changesets for package changes in a monorepo?▼

Changesets are standardized files that document version bumps and release notes for modified packages. When you edit code in packages/*, generate a .changeset/*.md file describing the change (patch for bug fixes, minor for features), then commit both your code and the changeset file together.

What's the difference between patch, minor, and major version bumps in changesets?▼

Patch fixes bugs without new functionality; minor adds backward-compatible features; major introduces breaking changes and requires explicit request. The Skill enforces this semantic versioning by guiding you to select the appropriate bump type based on your change description.

When should I create a changeset before opening a pull request?▼

Create a changeset whenever your PR modifies code in any package directory. This keeps release hygiene in sync with repository changes, ensures all affected packages are listed in a single changeset file, and prepares release notes before merge.

Can I use changesets across multiple packages in one monorepo?▼

Yes. Changesets document changes to multiple packages in a single .changeset/*.md file. List all affected packages and their version bumps, then commit the changeset alongside your code changes to maintain consistency across the monorepo.

Why does the changeset filename use a random three-word hyphenated format?▼

Random filenames prevent merge conflicts when multiple contributors create changesets in parallel. The hyphenated three-word format is standardized across the .changeset directory to ensure consistent, conflict-free naming during collaborative development.

Related Skills

Explore More Software Engineering Skills→
mia-cxmia-cx

setup-changesets

Configure and run changesets to publish versioned packages and changelogs.

Official
Intermediate
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate
pohlai88pohlai88

monorepo-workflows

Coordinates builds, tests, releases and publishing across Turborepo-based, pnpm-managed monorepos using Changesets for version management.

Community
Advanced
dhruvinrsonidhruvinrsoni

release-notes

Parse git history to generate changelogs and release notes.

Community
Advanced