Publishing Packages
SkillDev toolsConventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one. Use when adding or editing a changeset, versioning or releasing a package, or deciding whether a change to a publishable library needs a changelog entry.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Publishing Packages skill
What this skill tells your AI
The instructions your AI receives, as published by hashintel/hash in .agents/skills/publishing-packages/SKILL.md and read by ahel’s review.
npm-publishable packages in this repository are versioned and released with changesets. The changeset configuration, including which packages are ignored, lives in .changeset/config.json.
Changesets
A PR that changes an npm-publishable package adds a changeset file under .changeset/. The changeset text becomes the package's published changelog entry, so write it for the package's consumers:
- Describe the change as a consumer of the package experiences it: behaviour changes, bug fixes, and interface changes. Leave out implementation details that do not affect consumers, and do not mention this repository or its internal systems.
- Every sentence must apply to each package the changeset lists. When a PR changes several packages in different ways, write a separate changeset for each package.
- Use at most one paragraph per changeset.
A package's own AGENTS.md can carry further conventions, such as the bump level it accepts; check it before writing the changeset.
Signals
- GitHub stars
- 2k
- Forks
- 122
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
publishing-packages- Source
- github.com/hashintel/hash