SkillsAdd

smithery.ai

add-changeset

Create a changeset file for versioning and changelog generation. Use when the user asks to add a changeset, bump version, or prepare a release.

First seen Apr 2, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

release-and-changeset-best-practices Similar name
sonofmagic/skills

面向 weapp-vite monorepo 的 repoctl release、pnpm change intent 与 issue 交付工作流。适用于 `we…

184 installs
changeset-validation Similar name
openai/openai-agents-js

Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommi…

123 installs
changesets Similar name
oakoss/agent-skills

Changesets for versioning and changelog management in monorepos. Use when managing package vers…

116 installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,391 B
  • docs SUMMARY.md 164 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Add Changeset

First Todo list item: Find the code in this PR to get context.

Instructions

  1. If the user does not specify one of patch, minor, or major, use AskUserQuestion to prompt them:

- patch: Bug fixes, small changes (backwards compatible) - minor: New features (backwards compatible) - major: Breaking changes

Only prompt if they do not provide it

  1. Create a changeset file in .changeset/ directory with a descriptive name based on the feature or change (e.g., add-dark-mode.md, fix-login-bug.md, rename-config-fields.md)
  1. Add a todo at the end to verify the changeset with bun run changeset status

Example Changeset

File: .changeset/add-export-feature.md

---
"patchy-cli": patch
---

Add CSV export functionality for usage metrics

Changeset Format

---
"package-name": patch|minor|major
---

Description of the change (used in CHANGELOG)

Naming Convention

Name changeset files descriptively based on the change:

  • add-dark-mode.md (new feature)
  • fix-auth-timeout.md (bug fix)
  • rename-config-fields.md (refactor)
  • breaking-api-v2.md (breaking change)

Avoid random/generated filenames.