skills.rest
crowi
crowiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

crowi-changesets

Decides when to add changesets and selects bump levels and target packages for Crowi releases.

1.1k|165|Updated Aug 18, 2014
Search Tags:#release notes#pnpm#Monorepo#Versioning#SemVer#Changesets#ChangeLog
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-changesets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crowi-changesets
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-changesets
Command: npx skills add https://github.com/crowi/crowi --skill crowi-changesets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When committing features or fixes in the Crowi monorepo, developers often wonder whether a change warrants a changeset, which semver bump level to pick, and which package to target. This Skill provides clear decision criteria so release notes for v2 alphas and stable are generated automatically from accumulated changesets.

Core Features & Use Cases

  • Add-or-skip decision rules: Add a changeset for user-visible features, fixes, and breaking changes; skip refactors, chores, tests, docs, and .claude/ updates.
  • Bump level guidance: Maps changes to patch (bug fixes, safe dependency bumps), minor (new features, endpoints, backward-compatible config), or major (breaking changes).
  • Package targeting: Routes changes to @crowi/api, @crowi/web, @crowi/api-contract, @crowi/plugin-api, or individual plugins.
  • Use Case: Before merging a PR that adds a new API endpoint, run pnpm changeset add, select @crowi/api with a minor bump, and write a one-line English summary for the release notes.

Quick Start

Ask the assistant whether your current uncommitted changes need a changeset and, if so, have it draft the bump level, target package, and summary text.

Frequently Asked Questions about crowi-changesets

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

FAQPage Schema
How do I add a changeset in a pnpm monorepo?▼

Run pnpm changeset add to interactively pick the target package, bump level, and summary. This creates a markdown file under .changeset/ that accumulates until release, when release notes are generated automatically.

When should I add a changeset for a commit?▼

Add one changeset per unit of user value: features, bug fixes, and breaking changes. Skip internal refactors, cleanups, lint fixes, test-only changes, and documentation updates that produce no user-visible change.

How do I choose between patch, minor, and major bump levels?▼

Use patch for bug fixes and semver-safe dependency bumps, minor for new features, endpoints, or backward-compatible config additions, and major for breaking changes like API removals or newly required configuration.

Which package should a changeset target in a monorepo?▼

Target the package whose behavior changed: @crowi/api for API behavior, @crowi/web for UI changes, @crowi/api-contract for contract changes, and the specific plugin for single-plugin updates.

Should changeset summaries be wrapped across multiple lines?▼

No, keep each changeset summary as a single line per paragraph. GitHub Releases and Version PRs render summaries as GFM, where hard-wrapped lines become unwanted line breaks.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

release-notes-writer

Generate markdown release notes from git commits and pull requests.

Community
Intermediate
saleorsaleor
29

creating-changesets

Automate Changesets semantic versioning workflows in Node.js monorepos with Git and PNPM.

Official
Advanced
papertapeaipapertapeai

release-changelog

Generate stable release changelogs from git commits, changesets, and merged pull requests.

Community
Advanced
reaatechreaatech
2

Changelog Generation

Generate CHANGELOG.md entries and version bumps from conventional commits using Changesets.

Community
Advanced