changeset
Create changesets for version bump, release notes, changelog, PR description, semver patch/minor/major, breaking changes, and documentation updates after code changes
Best use case
changeset is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create changesets for version bump, release notes, changelog, PR description, semver patch/minor/major, breaking changes, and documentation updates after code changes
Teams using changeset should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/changeset/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How changeset Compares
| Feature / Agent | changeset | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create changesets for version bump, release notes, changelog, PR description, semver patch/minor/major, breaking changes, and documentation updates after code changes
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create Changesets and PR
## Overview
Generate changesets, update documentation, draft blog entries, and prepare PR description for user-facing changes.
## Steps
1. **Analyze changes**
- Compare current branch to `master` to identify modified packages
- Group changes by impact type (feature, fix, breaking)
- Identify transitive dependencies that expose the change
2. **Determine affected packages**
- Include directly modified packages
- Add transitive dependents when interfaces/behaviors are exposed:
- `@data-client/endpoint` → also select `@data-client/rest`, `@data-client/graphql`
- `@data-client/core` or `@data-client/normalizr` → also select `@data-client/react`, `@data-client/vue`
3. **Run changesets**
- Run `yarn changeset` once per distinct change
- Select all affected packages (direct + transitive)
- Choose appropriate version bump (patch/minor/major)
- For packages under 1.0, use minor for breaking changes
4. **Update documentation**
- Update primary docs in `docs/` for any changed public APIs
- Search for all usages of changed APIs across `docs/`, `packages/*/README.md`, and root `README.md`
- Update all found references to reflect new behavior, signatures, or deprecations
- For new exports: add to relevant API reference pages
5. **Update release blog**
- Find the latest draft blog post in `website/blog/` (has `draft: true` in frontmatter)
- Add the change following `@website/blog/.cursor/rules/blog-posts.mdc`:
- Place in appropriate conceptual category section
- Include code example if applicable
- Link to PR/commit and relevant docs
- For breaking changes: add to summary's Breaking Changes section with anchor link
6. **Generate PR description**
- Output a PR description for the user to copy/paste using @.github/PULL_REQUEST_TEMPLATE.md format
- Fill in the sections based on the analyzed changes
- Link related issues if known
- Summarize motivation from changeset descriptions
- Describe solution at a high level first (not implementation details)
- Include any mermaid diagrams that might help convey key concepts, especially if one was present in a plan.md
- Drop 'Open questions' section if no relevant content
- Keep in mind you are a chat agent talking in markdown, so cannot start a markdown block without escaping the contents.
## Changeset Format
- **First line**: Action verb ("Add", "Fix", "Update", "Remove")
- **Breaking**: Prefix with `BREAKING CHANGE:` or `BREAKING:`
- **Body**: 1–3 lines describing outcome, not implementation
- **New exports**: Use "New exports:" with bullet list
## Code Examples in Changesets
- Fixes: `// Before: ... ❌` `// After: ... ✓`
- Breaking changes: Use `#### Before` and `#### After` headers
- Multiple use cases: Separate with brief labels
## Markdown Formatting
Follow `@.cursor/rules/markdown-formatting.mdc` for all markdown content including the PR desc.Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
privgraph
Privacy and security annotation for Mermaid diagrams. Use this skill when: (1) a user shares or creates a Mermaid flowchart or sequence diagram and asks for privacy, security, or compliance review, (2) a user asks to annotate a diagram with data classifications, controls, trust boundaries, or compliance scope, (3) a user mentions 'privgraph', '@pg:', or 'risk-informed diagram', (4) a user asks about data flow risks, missing controls, or GDPR/HIPAA/PCI compliance gaps in an architecture diagram, (5) a user is writing a design doc with Mermaid diagrams and wants privacy/security feedback embedded in the diagram itself. Do NOT use for general Mermaid syntax help, diagram styling, or non-security topics.
prisma-workflow
Prisma workflow for schema changes, migrations, and common pitfalls in this repo.
prisma-v7
Expert guidance for Prisma ORM v7 (7.0+). Use when working with Prisma schema files, migrations, Prisma Client queries, database setup, or when the user mentions Prisma, schema.prisma, @prisma/client, database models, or ORM. Covers ESM modules, driver adapters, prisma.config.ts, Rust-free client, and migration from v6.
prisma-orm
Type-safe database access with Prisma ORM. Covers schema design, migrations, relations, queries, and TypeScript integration. Use when working with Prisma, database modeling, or building type-safe data layers for Node.js/TypeScript projects.
prisma-expert
Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.
prisma-docs
Local Prisma documentation reference. Use when asked about Prisma ORM, Prisma Client, Prisma Schema, migrations, database queries, Prisma Accelerate, or Prisma Postgres.
prisma-database-setup
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prioritize
Prioritize tasks and issues to determine what to work on and in what order. Use after identification, when planning work, or when unsure what to do next. This is the third system in the 5-system framework.
principles
Provides development principles, guidelines, and VibeCoder guidance. Use when user mentions 原則, principles, ガイドライン, guidelines, VibeCoder, 安全性, safety, 差分編集, diff-aware. Triggers: 原則, principles, ガイドライン, VibeCoder, 安全性, 差分編集. Do not use for actual implementation - use impl skill instead.
principal-engineer
Principal Engineer Skill
premium-ui-systems
Comprehensive system for building exceptional, production-ready UIs that avoid generic "vibe-coded" aesthetics. Use when building any web interface (dashboards, landing pages, SaaS products, React components, HTML/CSS layouts) to create distinctive, systematically premium designs. Covers hierarchy-first methodology, systematic design tokens, glassmorphism patterns, component libraries, creative direction, and avoiding AI-generated template aesthetics. Applies to Next.js, React, HTML/CSS, Tailwind, or any frontend stack.