release

Automates version bumping, tagging, and GitHub release creation for the barwise monorepo.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/semantic-praxis/barwise --skill release-semantic-praxis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/semantic-praxis/barwise/tree/main/.claude/skills/release
Command: npx skills add https://github.com/semantic-praxis/barwise --skill release-semantic-praxis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a barwise release involves a fragile sequence of npm version bumps, workspace dependency rewrites, version-sync updates, and tutorial regeneration, where skipping any step fails CI. This Skill encodes the exact commands and gotchas so releases succeed on the first attempt. ## Core Features & Use Cases - Coordinated version bump: Runs npm version across all workspaces with the correct flags, then rewrites internal @barwise/* dependency refs and refreshes the lockfile so npm ci passes. - Version-sync enforcement: Reminds you to bump the pinned SERVER_VERSION in packages/mcp/src/server.ts and regenerate the tutorial Markdown, both guarded by drift tests. - GitHub release creation: Tags the release, pushes to main, and creates the GitHub release that triggers the artifact build workflow (VSIX, CLI bundle, MCP bundle, SHA256SUMS). - Use Case: After merging a set of PRs to main, invoke this Skill to bump from v1.2.0 to v1.3.0, tag it, and publish the GitHub release without tripping the workspace-dependency or version-sync CI failures. ## Quick Start Cut a new patch release of barwise, bumping all package versions, tagging the commit, and creating the GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I bump versions across an npm workspaces monorepo?▼

Run `npm version patch --workspaces --include-workspace-root --no-git-tag-version --no-workspaces-update` from the repo root. Then manually rewrite internal `@barwise/*` dependency refs in each `packages/*/package.json` and run `npm install` to refresh the lockfile.

How do I create a GitHub release that builds artifacts?▼

Tag the release commit with `git tag -a v$VER` and push with `git push origin main --tags`, then run `gh release create v1.3.0 --generate-notes`. The release.yml workflow builds and attaches the VSIX, CLI bundle, MCP bundle, and SHA256SUMS.

Why does npm ci fail after bumping workspace versions?▼

The `--no-workspaces-update` flag leaves internal `@barwise/*` dependency refs at the previous version, so `npm ci` tries to fetch the old version from the public registry. Rewrite those refs to the new version and run `npm install` to refresh the lockfile.

What extra steps does a barwise release require beyond npm version?▼

You must bump the pinned `SERVER_VERSION` in `packages/mcp/src/server.ts` (a version-sync test asserts it matches package.json) and run `npm run regen:tutorial` because the committed tutorial stamps the tool version and has a drift test.

When should I run the Phase A architecture review?▼

Run it at minor releases: walk the scenario catalog in `docs/architecture-scenarios.md`, refresh the reflexion snapshot via `npm run arch:triage -- --base <last-release-tag>`, and commit a dated `docs/REPO_REVIEW-<YYYY-MM-DD>.md`.