changeset

Generate changesets and release notes from code changes in multi-package projects.

2.0k|99|Updated Feb 15, 2019
One-click install
npx skills add https://github.com/reactive/data-client --skill changeset-reactive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/reactive/data-client/tree/main/.cursor/skills/changeset
Command: npx skills add https://github.com/reactive/data-client --skill changeset-reactive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of changesets and PR descriptions for code changes, streamlining version bumps, release notes, and documentation updates.

Core Features & Use Cases

  • Changeset generation: Create changesets for patches, minor, or major updates based on changed packages.
  • Documentation and release notes: Draft release notes and update docs references automatically.
  • PR description drafting: Prepare concise PR descriptions aligned with changesets to accelerate reviews.

Quick Start

Generate a changeset and PR description for the upcoming release from your current branch.

Frequently Asked Questions about changeset

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

FAQPage Schema
How do I auto-generate changesets and release notes from code changes?

You can auto-generate changesets and release notes by analyzing code changes to detect affected packages, classify impact as feature, fix, or breaking, and produce structured output for versioned releases.

How do release notes work for multi-package monorepo projects?

Release notes for multi-package projects coordinate affected packages across the repository, classifying each change's impact and compiling structured documentation updates as part of the release workflow.

Can I draft PR descriptions aligned with my changesets automatically?

Yes, PR descriptions can be drafted automatically alongside changesets, summarizing code changes and impact classifications to accelerate the review process.

What is the best way to classify version bump impact for breaking changes?

Classifying version bump impact involves detecting changed packages and categorizing updates as patches, minor features, or major breaking changes to determine the correct version increment.

Does this changeset workflow apply to multi-repo projects?

Yes, this changeset workflow applies to both multi-repo and multi-package projects, coordinating affected packages and documentation updates across distributed codebases.

When do I need to generate structured changesets for versioned releases?

You need structured changesets when preparing versioned releases that require coordinated version bumps, release notes, and documentation updates across multiple affected packages.