Use when preparing, validating, or publishing a release for the laive repository. Applies the repo's AGENTS.md release policy, checks CHANGELOG.md, determines the semver bump, runs release checks, prepares versions with scripts/release.mjs, publishes npm when requested, and creates or updates the matching GitHub release from the changelog.
Use this skill only inside the laive repository.
Read these files before taking release actions:
AGENTS.mdCHANGELOG.mdpackage.jsondocs/release-process.mdmajor: breaking CLI, MCP, installer, or artifact-layout changesminor: new end-user capability or automationpatch: non-breaking fixes and clarificationsCHANGELOG.md has user-visible bullets under ## Unreleased.### Features, , and ### Fixes### Maintenancenode ./scripts/release.mjs prepare <patch|minor|major> --json
node ./scripts/release.mjs check
node ./scripts/release.mjs prepare <patch|minor|major> --apply
Only publish when the user explicitly asks.
Manual publish sequence:
git add CHANGELOG.md package.json packages/*/package.json
git commit -m "chore(release): vX.Y.Z"
git tag vX.Y.Z
npm publish --access public
After npm publish and tag push, create or update the GitHub release for the same version. Use the matching CHANGELOG.md section as the release body.
Example flow:
gh release view vX.Y.Z || gh release create vX.Y.Z --title "vX.Y.Z" --notes-file /tmp/laive-vX.Y.Z-release-notes.md
If the release already exists, use:
gh release edit vX.Y.Z --title "vX.Y.Z" --notes-file /tmp/laive-vX.Y.Z-release-notes.md
CHANGELOG.md.Features / Fixes / Maintenance for both ## Unreleased and versioned sections.