wip-release_skill

This skill automates local release workflows by bumping versions, updating docs, and publishing across registries and repositories.
  • Python

2.5k

GitHub Stars

8

Bundled Files

5 months ago

Catalog Refreshed

7 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill wip-release

  • _meta.json638 B
  • CHANGELOG.md1.2 KB
  • cli.js1.6 KB
  • core.mjs12.4 KB
  • package.json738 B
  • README.md1.9 KB
  • REFERENCE.md3.3 KB
  • SKILL.md2.1 KB

Overview

This skill provides a local release pipeline that automates version bumps, changelog updates, and publishing to npm and GitHub. It runs as a single command to perform the full release flow or as a dry run to preview changes. The tool is designed for projects that follow package.json-based releases and semantic versioning.

How this skill works

The command inspects the project version, bumps semver according to the chosen level (patch, minor, major), and appends release notes to the changelog. It updates the skill documentation file if it contains a YAML version frontmatter, creates a git tag, and optionally publishes the package to npm and pushes the tag to GitHub. Flags like --dry-run and --no-publish allow previewing or skipping registry publication while still performing versioning and tagging.

When to use it

  • After merging a change to main when you need to create a new release
  • When releasing any package that follows package.json-based versioning
  • When you want to bump version, update changelog, and tag in one step
  • To preview the release steps without making changes (use --dry-run)
  • To bump and tag without publishing to registries (use --no-publish)

Best practices

  • Run on the main branch after merging the pull request to ensure tags and pushes succeed
  • Use --dry-run first to verify changes before committing or publishing
  • Keep a valid npm token available in the configured secrets path for automated publishing
  • Ensure the project has a package.json; the tool expects package-based projects
  • Include a YAML version field in the skill documentation frontmatter if you want it updated automatically

Example use cases

  • Create a patch release that fixes a bug and publish to npm in one command
  • Perform a minor release with release notes and push the git tag using --no-publish to defer registry publishing
  • Run a dry run to confirm the changelog and version bump before the actual release
  • Automate local release steps as part of a release checklist for multiple packages
  • Archive and tag archived skill versions for backup and indexing workflows

FAQ

Verify the configured secrets file exists and that any required CLI (e.g., 1Password CLI) is installed and authenticated.

Why did the push fail?

Branch protection or missing permissions can block pushes. Confirm you are on the main branch after merging and have push rights.

Why wasn't the skill documentation updated?

The documentation is updated only when it contains a YAML frontmatter with a version field between frontmatter markers.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational