skills.rest
kjfsm
kjfsmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changeset-flow

Identify affected packages and create pnpm changeset records for npm releases.

1|Updated Apr 15, 2026
Search Tags:#git#workflow#release#pnpm#monorepo#semantic#changeset
One-click install
npx skills add https://github.com/kjfsm/notion-headless-cms --skill changeset-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changeset-flow
Source: https://github.com/kjfsm/notion-headless-cms/tree/main/.claude/skills/changeset-flow
Command: npx skills add https://github.com/kjfsm/notion-headless-cms --skill changeset-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that changes in packages/** which affect npm releases are documented using changesets, preventing untracked changes from slipping into a release.

Core Features & Use Cases

  • Automated changelog entry guidance: Guides contributors to create appropriate changesets for affected packages.
  • Release governance: Enforces that PRs touching packages/** are accompanied by changeset entries to ensure correct version bumps.
  • Use Case: When a PR changes code in multiple packages, generate and include changesets for all impacted packages to maintain release consistency.

Quick Start

Run the interactive changeset flow to document modifications for affected packages using pnpm changeset.

Frequently Asked Questions about changeset-flow

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

FAQPage Schema
How do I ensure changesets are created for all affected packages in a pnpm monorepo?▼

Changeset flow identifies and creates changeset records for any package under packages/ that would affect npm releases. It scans modified files across the repository and ensures changesets are created for all affected packages when PRs introduce changes, preventing untracked releases.

What happens if a PR modifies code in multiple packages without adding changeset entries?▼

Without changeset entries, CI checks will fail because changeset flow enforces that PRs touching packages/** must be accompanied by changeset entries. You must generate and include changesets for all impacted packages to maintain release consistency.

Do I need to mark public packages for release manually when using changeset flow?▼

Yes, changeset flow requires public packages to be explicitly marked for release. This step must be completed before CI checks run, using the interactive pnpm changeset tooling to document modifications for the affected packages.

How does changeset flow handle version bumps for npm releases in a monorepo?▼

Changeset flow handles version bumps by guiding contributors to create appropriate changeset entries for affected packages. When a PR changes code in multiple packages, it generates changesets to ensure correct semantic version bumps and maintain release consistency.

Can I use changeset flow for automated changelog entry guidance in a pnpm workspace?▼

Yes, changeset flow provides automated changelog entry guidance by guiding contributors to create appropriate changesets for affected packages. It ensures modifications under packages/** are properly documented before npm releases.

Related Skills

Explore More Software Engineering Skills→
growilabsgrowilabs
1.5k

monorepo-overview

Explain GROWI's pnpm workspace and Turborepo orchestration with changeset-based versioning.

Official
Intermediate
hdkz-devhdkz-dev

changeset-management

Manage versioning, changelogs, and release tagging for monorepos using Changesets.

Community
Intermediate
d-o-hubd-o-hub
4

github-ci-guardrails

Validate atomic commits and GitHub Actions checks before merging pull requests.

Community
Intermediate
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced