How do I install the Changeset skill?

Run npx skillmds@latest add diegosouzapw/changeset in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Changeset safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changeset?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changeset free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changeset?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changeset by diegosouzapw — Agent Skill

Name: Changeset
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

File contents

Create Changesets and PR

Overview

Generate changesets, update documentation, draft blog entries, and prepare PR description for user-facing changes.

Steps

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
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
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
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
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
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.

---name: changesetdescription: Create changesets for version bump, release notes, changelog, PR description, semver patch/minor/major, breaking changes, and documentation updates after code changes---# Create Changesets and PR## OverviewGenerate changesets, update documentation, draft blog entries, and prepare PR description for user-facing changes.## Steps1. **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 change2. **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 changes4. **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 pages5. **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 link6. **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 FormattingFollow `@.cursor/rules/markdown-formatting.mdc` for all markdown content including the PR desc.

Frequently asked questions

Changeset