# Sampo Changeset > Create or update changesets to describe public API changes, and trigger changelog generation and release planning. Use when this capability is needed. - Skill: `tomevault-io/sampo-changeset` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/sampo-changeset` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/sampo-changeset/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/sampo-changeset --- [Sampo](https://github.com/bruits/sampo) is a tool to automate changelogs, versioning, and publishing. It uses changesets (markdown files describing changes explicitly) to bump versions (in SemVer format), generate changelogs (human-readable files listing changes), and publish packages (to their respective registries). See [CONTRIBUTING.md](/CONTRIBUTING.md#writing-changesets) for changeset redaction guidelines. ## Creating New Changesets To create a changeset non-interactively: ```sh sampo add -p -b -m "" ``` Where `` is `major`, `minor`, or `patch`. Use `-p` multiple times to target several packages. Prefix with the ecosystem to disambiguate: `-p cargo/my-crate`. When `changesets.tags` is configured, use `-t ` to categorize the changeset. ## Updating Existing Changesets Pending changesets are stored in the `.sampo/changesets` directory. You can edit these markdown files directly, as long as you follow the guidelines above and Sampo format (read `.sampo/changeset.md.example` for reference). --- > Source: [bruits/sampo](https://github.com/bruits/sampo) — distributed by [TomeVault](https://tomevault.io).