skills.rest
isreal916
isreal916COMMUNITY
Explore all skills by this author →
GitHub

add-changeset

Creates changelog entries for pull requests using the changesets CLI.

Updated Aug 10, 2026
Search Tags:#changelog#pull request#release#semver#solidity#changeset#openzeppelin
One-click install
npx skills add https://github.com/isreal916/pistis --skill add-changeset-isreal916
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-changeset
Source: https://github.com/isreal916/pistis/tree/main/contracts/lib/openzeppelin-contracts/.claude/skills/add-changeset
Command: npx skills add https://github.com/isreal916/pistis --skill add-changeset-isreal916

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the OpenZeppelin Contracts repository need consistent, machine-readable changelog entries for every PR that changes user-visible contract behavior, and this Skill decides when a changeset is required and writes it in the correct format. ## Core Features & Use Cases - Decision Guidance: Determines whether a PR needs a changeset based on user-visible behavior changes, skipping NatSpec-only edits, internal refactors, and test-only changes. - Severity Selection: Maps changes to patch (bug fixes, gas optimizations) or minor (new contracts, extensions, public functions) semver bumps via npx changeset add. - Format Enforcement: Produces entries with a backtick-quoted component name, imperative mood, and a single sentence, matching the release workflow's concatenation rules. - Use Case: After adding a new function to an ERC-20 extension, run this Skill to generate a properly formatted .changeset/ file so the changeset-bot check passes on your PR. ## Quick Start Ask the assistant to add a changeset for the current pull request describing the contract change you just made.

Frequently Asked Questions about add-changeset

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

FAQPage Schema
How do I add a changeset to a pull request?▼

Run npx changeset add in the repository root. The CLI prompts for a semver severity (patch or minor), then opens an editor where you write a one-sentence description of the change, producing a file in the .changeset/ directory.

When should I add a changeset to my PR?▼

Add a changeset whenever the PR changes user-visible contract behavior: new functions, contracts, extensions, events, errors, interface IDs, or bug fixes that change outputs. Skip it for NatSpec-only edits, internal refactors, test-only changes, and CI or dependency updates.

What is the difference between patch and minor changeset severity?▼

Patch covers bug fixes and gas optimizations with no API surface change, while minor covers new contracts, extensions, or public functions on existing contracts. Contributors never select major; major version bumps are coordinated by maintainers.

What should I do if the changeset-bot says no changeset found?▼

If the PR legitimately needs no changeset (for example NatSpec-only edits), leave a comment on the PR justifying the omission. A maintainer can then apply the ignore-changeset label to satisfy the check.

What format should a changeset entry follow?▼

Start with the affected component name in backticks, followed by a colon and one imperative-mood sentence describing the change. Avoid bullet points, headings, and multi-paragraph prose, since the release workflow concatenates entries verbatim.

Related Skills

Explore More Software Engineering Skills→
dhntdhnt

update-pr-description

Rewrite pull request titles and bodies to match the current diff.

Official
Intermediate
reaatechreaatech
2

Changelog Generation

Generate CHANGELOG.md entries and version bumps from conventional commits using Changesets.

Community
Advanced
urufu-labsurufu-labs
1

add-changeset

Creates changeset changelog entries for pull requests modifying contract behavior.

Official
Basic
garden-cogarden-co
154

changeset

Generate .changeset files for package version bumps and changelog entries in monorepos.

Official
Intermediate