Pre Release
Validate Changesets in the Sandcastle repo are user-facing, grouped, and ready before you cut a release.
Install
npx skills add https://github.com/mattpocock/sandcastle --skill pre-releaseWhat is this skill?
- Audits every file under `.changeset` for release-note quality
- Three rules: user-facing only, related changes grouped, no maintainer/implementation detail
- Explicit contrast—changesets are not commit messages
- Ends with a commit of fixes; model invocation disabled for controlled maintainer runs
Adoption & trust: 8 installs on skills.sh; 5.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Release Skillsjimliu/baoyu-skills
Changelog Automationwshobson/agents
Msstore Cligithub/awesome-copilot
Changelog Generatorcomposiohq/awesome-claude-skills
Shopify App Store Reviewshopify/shopify-ai-toolkit
Shipping And Launchaddyosmani/agent-skills
Journey fit
Primary fit
Ship/Launch is where versioned packages leave the repo; this skill is the last editorial gate on .changeset content. Launch subphase covers pre-release publishing hygiene—changeset copy is what end users read in release notes pipelines.
Common Questions / FAQ
Is Pre Release safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Pre Release
Check all of the files in the `.changeset` directory. For the changesets as a whole, check the following: - Each changeset should be about a user-facing feature. Internal refactors or things that don't affect users should not be added as changesets. - Related changes should be grouped under a single changeset. - Changesets are user-facing, not maintainer-facing. They should not specify implementation details, or how a feature was made. They should only specify the user-facing change, and why it was made. Changesets !== commit messages. Once done, commit your changes.