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.