// Guided npm publish workflow — version bump, quality gate, build, publish, tag
Scaffold and implement a new MCP tool end-to-end — endpoint, handler, registration, docs
Debug a malfunctioning MCP tool — trace the full request lifecycle to find the issue
Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document
Post-task retrospective — captures what worked, what went wrong, writes lessons to auto-memory
Review code for bugs, MCP protocol violations, consistency issues, and convention adherence
Update documentation after tool changes — TOOLS.md, skill.md, README, INSTALLATION.md
| name | publish |
| description | Guided npm publish workflow — version bump, quality gate, build, publish, tag |
| argument-hint | [version: "patch", "minor", "major", or explicit like "1.1.0"] |
Prepare and publish a new version: $ARGUMENTS
This skill guides through the full release process. It does NOT auto-publish — it pauses for user confirmation at key points.
package.json$ARGUMENTS (default: patch)Current: X.Y.Z → New: A.B.CGet user confirmation before proceeding.
Verify the codebase is ready:
git status — working tree should be clean (no uncommitted changes)git branch — should be on main branchpackage.json, server.json, src/index.tsnpm run format:check — formatting is cleannpm run typecheck — no type errorsnpm run lint — no lint errorsnpm run test — all tests passnpm run build — build succeedsIf ANY check fails, stop and report. Do not continue with a broken build.
Update version in all 3 locations:
package.json → versionserver.json → version and packages[0].versionsrc/index.ts → server constructor versionnpm run build
The dist/ directory must reflect the new version.
Show git diff so the user can verify:
Get user confirmation before committing.
git add package.json server.json src/index.ts dist/
git commit -m "chore: Bump version to A.B.C"
git tag vA.B.C
Show the command but DO NOT run it automatically:
npm publish
git push origin main --tags
Tell the user to run these commands themselves.