add-changeset

Creates changeset changelog entries for pull requests modifying contract behavior.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/urufu-labs/urufu-launchpad --skill add-changeset-urufu-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-changeset
Source: https://github.com/urufu-labs/urufu-launchpad/tree/main/contracts/lib/openzeppelin-contracts/.claude/skills/add-changeset
Command: npx skills add https://github.com/urufu-labs/urufu-launchpad --skill add-changeset-urufu-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors to the OpenZeppelin contracts repository often forget or misformat changelog entries, causing release notes to be incomplete or inconsistent. This Skill decides when a changeset is required and generates one in the exact format the release workflow expects. ## Core Features & Use Cases - Change Detection Guidance: Defines which PR changes require a changeset (new functions, contracts, events, errors, interface IDs) and which to skip (NatSpec-only edits, internal refactors, test-only changes). - Severity Selection: Maps changes to semver levels, using patch for bug fixes and gas optimizations and minor for new contracts, extensions, or public functions. - Format Enforcement: Produces entries with a backtick-quoted component name, a colon, and one imperative-mood sentence, matching the concatenation rules of the release workflow. - Use Case: After adding a new public function to an ERC-20 extension, run the changeset flow to produce a properly formatted .changeset/ entry before the changeset-bot flags the PR. ## Quick Start Ask the assistant to add a changeset for the current pull request describing the user-visible contract change.

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 for an OpenZeppelin contracts PR?▼

Run npx changeset add, choose the severity when prompted, and write one imperative sentence describing the change. The CLI creates a file in the .changeset/ directory that the release workflow concatenates into the changelog.

When should I skip adding a changeset?▼

Skip changesets for NatSpec-only edits, internal refactors with no observable effect, test or mock-only changes, and CI or dependency updates that do not alter the published contracts. If the bot flags the PR anyway, a maintainer can apply the ignore-changeset label.

What severity should a changeset use for a new public function?▼

Use minor for new contracts, new extensions, or new public functions on existing contracts. Use patch for bug fixes and gas optimizations with no API surface change. Major bumps are coordinated by maintainers, not contributors.

Why does the changeset-bot say no changeset found on my PR?▼

The bot posts that message when no file exists in the .changeset/ directory. Either add one with npx changeset add, or if the PR legitimately needs none, leave a comment justifying it so a maintainer can apply the ignore-changeset label.

What format does a changeset entry require?▼

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