Skill566 repo starsupdated 1mo ago

release-local

The release-local skill automates publishing a Changesets-based pnpm monorepo by checking for pending changesets, running version bumps, committing release files, and publishing to npm while pushing tags to GitHub. Use this when ready to release a new version of the monorepo, as it requires confirmations before versioning and publishing to prevent accidental releases.

View source Repository: open-harness

Install in Claude Code

Copy

git clone --depth 1 https://github.com/MaxGfeller/open-harness /tmp/release-local && cp -r /tmp/release-local/.claude/skills/release-local ~/.claude/skills/release-local

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

Run the release workflow from `RELEASING.md`.

Guardrails:

- Only run this on `main` unless the user explicitly wants a dry run elsewhere.
- Require a clean worktree before versioning or publishing.
- Ask for confirmation before creating the release commit.
- Ask for confirmation again before starting `pnpm release:publish`, because it publishes to npm, pushes the branch and tags to GitHub, and may require npm OTP entry.

Workflow:

1. Run `pnpm release:status` and confirm there are pending changesets.
2. Run `pnpm version-packages`.
3. Review the generated version bumps and changelog entries with the user.
4. Commit the release files with `Release packages` unless the user requests a different message.
5. Run `pnpm release:publish`.
6. Confirm that npm publish succeeded and that GitHub Releases were created or updated for the tags on `HEAD`.
7. If npm publish succeeded but GitHub release creation failed, rerun `pnpm release:github` after fixing the blocker.

If publish fails because of npm auth, OTP, or missing release notes, stop, report the exact blocker, and do not keep mutating the repo.