Menu
Versioning packages with changesets
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Coding patterns and conventions (package design, types, DI, docs)
Creating a new package in the monorepo
Running CI locally with Dagger
Debugging (source maps, cache, test failures)
DevContainer runtimes, CLI tools, and version parity with Dagger
Installing a package dependency
| name | versioning |
| description | Versioning packages with changesets |
Changesets docs: github.com/changesets/changesets Config:
../../../.changeset/config.json
This repo uses Changesets to track version bumps and generate changelogs. Every PR that changes a published package should include a changeset file.
After making your changes, run:
changeset
Follow the interactive prompts to:
patch, minor, major)This creates a file in .changeset/ (e.g. .changeset/brown-foxes-run.md). Commit it alongside your code changes.
Generated files look like:
---
"package-name": patch
---
Description of the change.
You can edit this file manually if you need to.
leyman/main (workspace package, never published)