skills.rest
vuluu2k
vuluu2kCOMMUNITY
Explore all skills by this author →
Website𝕏@vuluu2kGitHub

sbuilder-release

Documents the npm and MCP Registry release pipeline for sbuilder-mcp with failure recovery guidance.

Updated Aug 28, 2026
Search Tags:#changelog#versioning#github actions#release#npm publish#ci cd#MCP Registry
One-click install
npx skills add https://github.com/vuluu2k/sbuilder-mcp --skill sbuilder-release-vuluu2k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sbuilder-release
Source: https://github.com/vuluu2k/sbuilder-mcp/tree/main/.claude/skills/sbuilder-release
Command: npx skills add https://github.com/vuluu2k/sbuilder-mcp --skill sbuilder-release-vuluu2k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing sbuilder-mcp involves an auto-release GitHub workflow, version bump inference, changelog generation, and npm plus MCP Registry publishing, where several non-obvious pitfalls have already caused real release failures. This Skill preserves those hard-won facts so nobody re-derives them or repeats the mistakes. ## Core Features & Use Cases - Pipeline Reference: Explains the auto-release workflow end to end, from the build/test/smoke gate through bump selection, bilingual changelog, tagging, npm publish, and MCP Registry via GitHub OIDC. - Bump Rules: Clarifies that the version bump is read from the head commit subject alone (feat → minor, BREAKING CHANGE or ! → major, else patch), not the pushed range. - Failure Playbook: Records four real incidents, including duplicate gh workflow run dispatches, EOTP from non-automation npm tokens, and why failed release runs must never be re-run. - Use Case: A release to main failed with EOTP after the tag was pushed; consult this Skill to learn the token must be an npm automation token and how to recover by dispatching a fresh run. ## Quick Start Ask the AI to explain how to safely dispatch or recover an sbuilder-mcp release after a failed auto-release workflow run.

Frequently Asked Questions about sbuilder-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the sbuilder-mcp auto-release workflow choose the version bump?▼

The bump is read from the head commit subject alone: feat maps to minor, BREAKING CHANGE or an exclamation mark maps to major, and anything else is a patch. A workflow_dispatch run can pick its own bump explicitly.

How do I release sbuilder-mcp without CI?▼

Run npm run release, which invokes scripts/release.mjs as the offline path. It must keep the same changelog heading format and commit subject because the workflow prepends above the first version heading and matches the subject as its skip guard.

Why did the npm publish fail with EOTP in the release workflow?▼

EOTP occurs because NPM_ACCESS_TOKEN was a classic publish token, which still demands a one-time password that CI cannot supply. Use an npm automation token, or a granular token with read and write permissions.

Can I re-run a failed auto-release workflow run?▼

Never re-run a failed release run, because it replays the old commit whose package.json predates the release commit and bumps again. Instead dispatch a fresh run on main, whose resume mode publishes the missing version.

Why did gh workflow run start two release runs?▼

The gh workflow run command was observed starting two runs, with the second queuing behind the auto-release concurrency group. Cancel the duplicate after reading each run's dispatch inputs, since they are not interchangeable.

Related Skills

Explore More Software Engineering Skills→
devantler-techdevantler-tech
2

conventional-release

Write Conventional Commit PR titles and commit messages for automated releases.

Official
Intermediate
semicolon-devteamsemicolon-devteam

deploy-npm

Automate SEMO npm package deployment with version bumps, builds, publishes, and Slack alerts.

Official
Advanced
aizhimouaizhimou
1.2k

release-note-publisher

Convert release-branch commits into bilingual English and Chinese release notes and publish them to GitHub Releases.

Community
Advanced
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate