release-check
Automated readiness check to ensure a project is prepared for a new npm release.
Install
mkdir -p .claude/skills/release-check-mistralys && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15875" && unzip -o skill.zip -d .claude/skills/release-check-mistralys && rm skill.zipInstalls to .claude/skills/release-check-mistralys
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Pre-release readiness check for the @mistralys/persona-builder package. Run all checks before executing `npm version`. Use when: preparing a release, verifying release readiness, checking if the project is ready to publish.Key capabilities
- →Verify changelog version is ahead of package.json
- →Confirm no existing Git tag for new version
- →Run TypeScript type checks
- →Execute test suite
- →Build the project
How it works
The skill performs a series of checks, including version comparisons, Git tag verification, and build/test executions, to ensure the package is ready for release.
Inputs & outputs
When to use release-check
- →Prepare a release
- →Verify release readiness
- →Check npm publish status
About this skill
Release Check
For the full release flow and rationale, see docs/releasing.md.
Validates that the package is ready for release via npm version {VERSION}. Run all steps in order and report the result of each check before continuing to the next.
Release Flow Context
Releases follow a two-step sequence:
- Pre-release (this skill): All checks below must pass.
- Tag and publish:
npm version {VERSION}(auto-bumpspackage.json, creates a Git commit and tag), thennpm publish.
npm versioncreates the Git tag automatically. Therefore at release-check time,package.jsonstill holds the old version whileCHANGELOG.mdalready documents the new version. The version ahead check relies on this gap.
Procedure
1. Changelog version ahead check
Extract the topmost version from CHANGELOG.md (the first line matching ## vX.Y.Z). Read the version field from package.json. Parse both as semver and verify the changelog version is strictly greater than the package.json version.
Pass: Changelog version > package.json version.
Fail: They are equal (changelog not updated yet) or package.json is ahead (version was bumped without a changelog entry).
2. Git tag gap check
git tag --sort=-v:refname | head -5
Confirm that the changelog top version does not already have a corresponding Git tag in either form: with the v prefix (v2.4.0, the form npm version creates) or without (2.4.0, a hand-made tag that would collide with the release). Releases are never tagged by hand. A matching tag means this version has already been released.
Pass: Neither X.Y.Z nor vX.Y.Z exists for the changelog top version.
Fail: Matching tag found — changelog entry is a re-release of an already-tagged version.
3. TypeScript type check
npm run typecheck
Must complete with no errors. Fix all type errors before proceeding.
4. Test suite
npm test
All Vitest tests must pass. Zero failures and zero unresolved errors are required. Skipped tests are acceptable.
5. Build
npm run build
tsup must produce the dist/ output without errors. This confirms the package is publishable and catches any compilation issues not caught by typecheck alone (e.g., tsup-specific entry point resolution).
6. Git working tree
git status --short
git diff --name-only
Run this after the build. The working tree must be clean before running npm version; the build must not leave tracked files modified (dist/ is gitignored). Commit or stash any uncommitted changes first.
Pass Criteria
| Check | Expected result |
|---|---|
| Changelog version ahead | CHANGELOG.md version > package.json version (semver) |
| Git tag gap | No X.Y.Z or vX.Y.Z tag for the changelog top version |
| TypeScript type check | Exit 0, no errors |
| Test suite | All tests pass, exit 0 |
| Build | dist/ produced without errors, exit 0 |
| Git working tree | No uncommitted changes |
All checks must pass before proceeding.
Tagging and Publishing
Once all checks pass:
npm version <version> # e.g. npm version 2.4.0
npm publish
npm version automatically bumps package.json, creates a commit, and creates the Git tag. Push the commit and the tag afterward, then create the GitHub release from that tag:
git push && git push origin v<version>
When not to use it
- →When `CHANGELOG.md` version is not strictly greater than `package.json` version
- →When a Git tag already exists for the changelog top version
- →When TypeScript type checks fail
Limitations
- →Requires `CHANGELOG.md` to be updated before `package.json`
- →Requires no existing Git tag for the new version
How it compares
This skill provides a structured, automated pre-release readiness check, ensuring all conditions are met before `npm version`, unlike manual verification.
Compared to similar skills
release-check side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-check (this skill) | 0 | 7mo | Review | Intermediate |
| agent-workflow-automation | 4 | 9mo | Review | Advanced |
| project-os | 1 | 10mo | Review | Intermediate |
| project-tooling | 1 | 7mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-workflow-automation
ruvnet
Agent skill for workflow-automation - invoke with $agent-workflow-automation
project-os
Peiiii
AI project OS for autonomous loop, automated orchestration, and rule-driven execution.
project-tooling
alinaqi
gh, vercel, supabase, render CLI and deployment platform setup
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
Release
tobagin
Create a new Keymaker release — analyze changes, bump version, update changelog/README/AppStream metadata, build, commit, tag, push, and create GitHub release
release
RajwanYair
Bump the version, update the changelog, tag, and publish a GitHub release for RegiLattice. Use when preparing a new release, updating version numbers, creating a CHANGELOG entry, or pushing a version tag to trigger the CI release workflow. Triggers on: 'bump version', 'release', 'publish', 'version'