skills.rest
firstsun-dev
firstsun-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-openspec

Audits, prepares, publishes, and finalizes OpenSpec releases via GitHub and Changesets.

3|1|Updated Apr 29, 2026
Search Tags:#release management#versioning#github#release notes#openspec#npm publish#changesets
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill release-openspec-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-openspec
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/release-openspec
Command: npx skills add https://github.com/firstsun-dev/skills --skill release-openspec-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Releasing an npm package with Changesets involves many fragile steps—auditing merged PRs for missing changesets, validating the automated Version Packages PR, waiting on merge queues, verifying npm/tags/GitHub Releases, and polishing release notes. This Skill turns that into a resumable state machine that inspects live GitHub state and takes only the next safe action. ## Core Features & Use Cases - Release audit: Classifies the repository into states like missing-tracking, awaiting-version-review, ready-to-publish, or complete, mapping merged PRs to changeset coverage. - Changeset and Version Packages PR management: Creates catch-up changeset PRs in temporary worktrees, validates the automated Version Packages PR against pending changesets, and respects human review gates and merge queues. - Publish verification and notes: Verifies npm version, git tag, and GitHub Release independently, then polishes release notes using the bundled reference guide; also supports beta releases via the release-prepare.yml workflow. - Use Case: Ask whether the open OpenSpec release PR is complete—the Skill audits merged work since the last stable tag, reports the exact state, and either pauses for human approval or continues the release. ## Quick Start Use the release-openspec skill to audit the current OpenSpec release state and take the next safe release step.

Frequently Asked Questions about release-openspec

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

FAQPage Schema
How do I release an npm package with Changesets on GitHub?▼

Run a release audit first: find the latest stable tag, map merged PRs to pending changesets, then validate the automated Version Packages PR from changeset-release/main. Merge it only after human approval and green checks, then verify npm, the git tag, and the GitHub Release.

How do I check if a Version Packages PR is ready to merge?▼

Confirm it targets main from changeset-release/main, compare base and head worktrees so every pending .changeset/*.md file is consumed, and verify package.json, CHANGELOG.md, and the proposed version agree. Then check required status checks and review state with gh pr view.

What should I do when merged PRs are missing changesets?▼

Create a catch-up changeset PR from current origin/main in a temporary worktree, using the exact package name and the highest required semantic bump. Validate with pnpm exec changeset status, open the PR, and pause for human approval rather than self-approving.

Can I cut a beta release without consuming changesets?▼

Yes. Trigger the existing release-prepare.yml workflow on main, which selects the beta version itself without consuming changesets or touching the stable Version Packages PR. Then verify the npm beta dist-tag, remote tag, and prerelease GitHub Release.

Why is my Version Packages PR stale after merging a changeset?▼

The Changesets action updates the PR only after a successful push run of release-prepare.yml on main. Confirm that workflow ran after the changeset landed, and never force-push changeset-release/main or create the Version Packages PR manually.

What happens if the release is interrupted mid-publish?▼

The workflow is resumable: each invocation re-inspects live GitHub state and classifies the release into a state such as publishing or needs-finalization. It verifies npm, tag, and GitHub Release independently and resumes from the first incomplete artifact instead of republishing.

Related Skills

Explore More Software Engineering Skills→
gancimgancim

release-changelog

Generate a stable release changelog from commits, changesets, and PR metadata.

Community
Advanced
papertapeaipapertapeai

release

Coordinate software releases with changelog drafting, version management, and npm publishing.

Community
Advanced
kubb-labskubb-labs
1.8k

pr

Enforces PR checklists, changeset creation, and release rules for monorepo contributions.

Official
Basic
devantler-techdevantler-tech
2

conventional-release

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

Official
Intermediate