| name | add-registry-changeset |
| description | Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR. |
Add a Registry Changeset
The hyperlane-registry repo uses changesets to track PR-level changes and drive npm releases of @hyperlane-xyz/registry. Every PR that touches the published surface (warp route configs, chain metadata, addresses, deployments) MUST carry a changeset, otherwise the merge bot blocks the PR and the published package falls behind. Skills that open registry PRs invoke this skill to write the changeset before committing.
Why a dedicated skill
- Single source of truth for filename / frontmatter / style / semver-bump conventions.
- Avoids per-skill drift — fresh deploys, route updates, chain extensions, address backfills, logo updates all need the same shape; encode it once.
- Closes the recurring miss where the PR-opening was done ad-hoc (user prompts the agent to "open a registry PR") and the agent forgets the changeset because it isn't in the parent skill's checklist.
Input
- Change summary (required) — one short sentence describing what the PR does. Past tense, lowercase, concise (CLAUDE.md style for changesets).
- Bump type (required) —
minor for new warp routes / new chains / new published assets; patch for updates / fixes / metadata tweaks to existing entries.
- Filename slug (optional) — short kebab-case identifier; if not provided, the agent picks a slug derived from the PR scope (e.g.
add-ikas-ethereum-igra, update-eth-arbitrum-base-fee-11bps, fix-katana-rpc). The auto-generated <adjective>-<noun>-<verb>.md names that the interactive CLI emits are also acceptable but discouraged — descriptive slugs are easier to scan in PR diffs.
