create-changesets

Generate semantic versioning changesets for pnpm monorepo packages.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill create-changesets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-changesets
Source: https://github.com/finger-gun/sisu/tree/main/.github/skills/create-changesets
Command: npx skills add https://github.com/finger-gun/sisu --skill create-changesets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the detection of repository changes and the generation of semantic versioning changesets to streamline releases across a multi-package monorepo.

Core Features & Use Cases

  • Automated change analysis across packages with independent versioning to prepare release notes.
  • Generates accurate changesets for breaking, minor, and patch changes aligned with the Changesets workflow.
  • Integrates with the monorepo tooling to maintain changelog consistency and release readiness.

Quick Start

Analyze the repository for changes and generate a changeset in the .changeset directory for the next release.

Frequently Asked Questions about create-changesets

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

FAQPage Schema
How do I automatically generate semantic changesets in a pnpm monorepo?

To generate semantic changesets in a pnpm monorepo, this skill analyzes repository changes and automatically creates versioning files in the .changeset directory. It identifies breaking, minor, and patch changes across packages with independent versioning to prepare releases.

What is the best way to prepare independent releases across multiple packages using turbo?

Preparing independent releases across multiple packages using turbo requires analyzing API changes and generating accurate semantic changesets. This skill detects repository updates and writes changeset files to maintain changelog consistency and release readiness across the monorepo.

Can I use changesets to automate release notes for independent versioning?

Yes, you can use changesets to automate release notes for independent versioning. This skill analyzes repository changes and generates appropriate semantic versioning changesets that document breaking, minor, and patch updates to streamline monorepo releases.

Do I need pnpm and turbo to generate changesets for independent versioning?

You need pnpm and turbo to effectively use this skill for generating changesets with independent versioning. The skill is specifically designed to apply to a pnpm monorepo using turbo, analyzing repository changes and storing results in the .changeset directory.

How does automated changeset generation handle breaking API changes in a monorepo?

Automated changeset generation handles breaking API changes by analyzing repository updates and generating accurate semantic versioning changesets. The skill identifies breaking changes across packages and writes them to the .changeset directory with clear rationale for the next release.

Why use changesets for semantic versioning instead of manual changelog updates in a monorepo?

Using changesets for semantic versioning instead of manual changelog updates ensures accuracy across a pnpm monorepo using turbo. This skill automates change detection and generates changeset files that reflect API changes, maintaining changelog consistency and release readiness.