
Changeset
- 1 installs
- Updated June 3, 2026
- alchemyplatform/alchemy-cli
changeset (alchemy-cli) is a skill that creates a changeset file describing user-facing changes and a semver bump type for the current branch.
About
This skill creates a changeset file documenting user-facing changes on the current branch for the @alchemy/cli package. It asks for or infers the semver bump type, inspects the git diff to understand what changed, and writes a summary focused on user-visible behavior. It then generates a kebab-case markdown file under .changeset in the exact changesets format. It enforces one changeset per logical change and never uses a major bump without explicit confirmation.
- Creates a changeset file describing user-facing changes for the current branch
- Determines patch, minor, or major bump and inspects git diff to write the summary
- Enforces one changeset per logical change and blocks major bumps without confirmation
Changeset by the numbers
- 1 all-time installs (skills.sh)
- Ranked #210 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
changeset capabilities & compatibility
- Capabilities
- changeset create · changelog entry
- Works with
- github
- Use cases
- ci cd · documentation
- Pricing
- Free
What changeset says it does
Create a changeset file describing user-facing changes for the current branch.
Never use `major` without explicit user confirmation.
npx skills add https://github.com/alchemyplatform/alchemy-cli --skill changesetAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | June 3, 2026 |
| Repository | alchemyplatform/alchemy-cli ↗ |
What it does
Create a changeset file recording a semver bump and user-facing summary for the current branch before release.
Who is it for?
Generating a properly formatted changeset entry for the @alchemy/cli package before opening or merging a PR.
Skip if: Applying a major bump without confirmation or modifying existing changeset files unless asked.
When should I use this skill?
When you have pending user-facing changes on a branch and need to record a changeset before release.
What you get
Writes a .changeset markdown file with the right bump type and a user-facing summary.
- .changeset/<kebab-case-name>.md file
By the numbers
- 5-step workflow
- 3 bump types (patch/minor/major)
Files
Create Changeset
Create a changeset file describing user-facing changes for the current branch.
Steps
1. Determine the bump type. If not provided by the user, ask which applies:
patch— bug fix or small tweakminor— new feature, command, or flagmajor— breaking change (removed/renamed command, changed output format)
2. Inspect recent changes. Run git diff main...HEAD --stat and read changed files to understand what changed.
3. Write a summary. Compose a 1-2 sentence description of the change from a user's perspective. Focus on what changed and why it matters, not implementation details.
4. Generate the changeset file. Create .changeset/<kebab-case-name>.md with this exact format:
---
"@alchemy/cli": <bump-type>
---
<summary>The kebab-case name should be descriptive (e.g., add-portfolio-command, fix-json-output). Do not use random words.
5. Confirm. Show the user the file path and contents for review.
Rules
- One changeset per logical change. If a PR has multiple independent changes, create multiple files.
- Never use
majorwithout explicit user confirmation. - The summary must describe user-visible behavior, not code changes.
- Do not modify existing changeset files unless asked.
Related skills
FAQ
What does the changeset skill do?
It inspects your branch's git diff, picks a patch, minor, or major bump, and writes a .changeset markdown file describing the user-facing change for @alchemy/cli.
Will it use a major bump automatically?
No. The docs state it never uses major without explicit user confirmation.