Pre Release
- 22 installs
- 7.1k repo stars
- Updated June 29, 2026
- mattpocock/sandcastle
Validate Changesets in the Sandcastle repo are user-facing, grouped, and ready before you cut a release.
About
Pre-release is a Release Management agent skill for maintainers of mattpocock’s Sandcastle monorepo who use Changesets to communicate what shipped. It walks the agent through every file in `.changeset` and enforces editorial rules: only user-visible features belong, related work shares one changeset, and prose must explain what changed for users and why—not how it was implemented. Internal refactors without user impact should be excluded. Because `disable-model-invocation` is set, you typically invoke it deliberately as a maintainer ritual rather than letting the model auto-fire mid-session. Solo builders running their own multi-package products get a repeatable pre-launch checklist that keeps changelog noise down and prevents duplicate or overly technical release entries. Finish by committing corrected changesets so CI and the release bot see consistent metadata.
- 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
Pre Release by the numbers
- 22 all-time installs (skills.sh)
- Ranked #169 of 257 Release Management skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mattpocock/sandcastle --skill pre-releaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 22 |
|---|---|
| repo stars | ★ 7.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 29, 2026 |
| Repository | mattpocock/sandcastle ↗ |
What it does
Validate Changesets in the Sandcastle repo are user-facing, grouped, and ready before you cut a release.
Files
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.
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.10.9k38.3k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.6.9k37.1k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.8k71.1k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.3k23.1k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4k234k
OnboardingInstall this skill to create your first LaunchDarkly boolean flag, add evaluation code, and prove OFF then ON behavior end-to-end after the SDK is in place.3.8k20FAQ
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.