skills.rest
openwop
openwopOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release

Automate OpenWOP spec-corpus releases with version bumping and verification.

1|Updated May 11, 2026
Search Tags:#version control#CI/CD#package management#release automation#software release
One-click install
npx skills add https://github.com/openwop/openwop --skill release-openwop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/openwop/openwop/tree/main/.claude/skills/release
Command: npx skills add https://github.com/openwop/openwop --skill release-openwop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of releasing new versions of the OpenWOP spec-corpus, ensuring that all steps are executed consistently and correctly.

Core Features & Use Cases

  • Version Lockstep: Ensures all component packages are released at the same version.
  • Changelog Collapse: Condenses the development changelog into a concise release notes block.
  • Pre-Publish Checks: Validates all artifacts before publication.
  • Post-Publish Verification: Confirms that all published artifacts are correct and functional.
  • Use Case: When preparing to release a new version of OpenWOP, this Skill will automate the entire release process, from version bumping to post-publish verification.

Quick Start

Run the skill with the target version as an argument: release 1.1.4.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate package version bumping and publish multiple packages in lockstep?▼

Automate package version bumping using this release Skill to enforce version lockstep for multiple packages, ensuring all component packages are released at the same version simultaneously.

What is the best way to condense development changelogs into concise release notes?▼

The best way to condense development changelogs is through the changelog collapse feature, which condenses the development changelog into a concise release notes block for your release.

Do I need npm, git, and GitHub CLI installed to automate software release workflows?▼

Yes, you need npm, git, and GitHub CLI installed, because this release automation requires all three dependencies to handle version bumping and post-publish verification correctly.

How to run pre-publish checks and post-publish verification for npm packages?▼

Run pre-publish checks and post-publish verification by executing the release Skill, which validates all artifacts before publication and confirms published artifacts are correct and functional.

Why should I use release automation for version control instead of manual package publishing?▼

Use release automation instead of manual package publishing to ensure consistency and correctness across the entire release process, preventing human error during version lockstep and artifact validation.

Can I use this release automation for a single package or is it only for multiple package lockstep?▼

This release automation handles version lockstep for multiple packages, but it effectively ensures all component packages are publish-ready and validates artifacts regardless of the package count.

Related Skills

Explore More Software Engineering Skills→
andymaiandymai
20

release-flow

Coordinate software package releases to the npm registry and web interfaces.

Community
Advanced
dotnetdotnet
209

ci-validation-gates

Validate semver, npm token types, and release events in GitHub Actions workflows.

Official
Advanced
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate
udecodeudecode
434

changeset

Automates creation and management of release changesets for versioning and changelogs.

Official
Intermediate