Automates end-to-end npm releases for Rove with changeset detection, gates, and CI monitoring.
npx skills add https://github.com/Sma1lboy/rove --skill release-sma1lboy
Please help me install this Agent Skill. Skill: release Source: https://github.com/Sma1lboy/rove/tree/main/.claude/skills/release Command: npx skills add https://github.com/Sma1lboy/rove --skill release-sma1lboy
.changeset/*.md files, computes the resulting bump, and stops to confirm when an unexpected minor or major changeset would promote the release. - Gate Enforcement: Runs lint, typecheck, tests, build, and the golden perf suite locally before invoking scripts/release.sh, which handles version, changelog, commit, tag, and push. - CI Monitoring & Diagnosis: Polls the GitHub Actions Release workflow with gh, verifies the published versions on npm, and maps CI failures (npm token errors, registry 404, tag mismatch, E409) to precise remediation steps. - Use Case: A maintainer says "cut a release" — the Skill checks whether the automatic changesets workflow already handles it, otherwise runs the local release flow, confirms the tag pushed to main, and reports the published version and release URL. ## Quick Start Ask the agent to cut a release for Rove and it will detect the bump, run the gates, tag and push, then watch CI until the new version is live on npm.High-intent search queries and answers about installing and using this skill.
Run the release flow which inspects pending .changeset/*.md files to compute the semver bump, executes lint, typecheck, test, and build gates, then runs scripts/release.sh to version, commit, tag, and push. The tag push triggers the GitHub Actions Release workflow that publishes to npm.
Use gh run list --workflow=release.yml to find the run for the tag, then gh run watch <run-id> --exit-status to block until completion. Afterwards verify with npm view @sma1lboy/rove@<version> and gh release view to confirm the publish actually landed.
A pending changeset file carries a minor or major bump type in its frontmatter, and changeset version takes the maximum of all pending bumps. The Skill flags this before releasing and asks for confirmation, since an upstream changeset can silently promote the release.
The NPM_TOKEN secret is missing, expired, or has the wrong scope. Token rotation is a manual task in repository Settings under secrets, and republishing after fixing it requires a new version because npm will not overwrite an existing one.
No. The Skill forbids force-pushes, retagging over existing tags, and republishing the same version. A failed publish after a tag push requires a new patch version, while a red CI before tagging lets you fix on main and re-run scripts/release.sh in resume mode.
daangnDetects changed public packages in Git diffs and writes approved Korean changeset files.
antfuResolve npm package versions and dist-tags without full registry manifests.
emdash-cmsApply diagnosed bug fixes and stage changes after passing tests, lint, and typecheck.
mia-cxAutomate software releases with versioning, changelog generation, and GitHub releases.