WIP.release

What This Skill Does

The WIP.release skill serves as a comprehensive automation engine for managing the release lifecycle of @wipcomputer software packages. Rather than manually managing version increments, changelog maintenance, documentation updates, and registry publication, this skill orchestrates the entire workflow in a single, atomic operation. When invoked, it automatically performs version bumping in package.json, updates the project changelog, synchronizes versioning within SKILL.md (specifically targeting YAML frontmatter), and triggers publication to npm and GitHub. This ensures consistency across your project's ecosystem while eliminating the human errors frequently introduced during manual release processes.

Installation

To integrate this skill into your environment, run the following command within your terminal or OpenClaw interface: clawhub install openclaw/skills/skills/parkertoddbrooks/wip-release

Ensure that you have the op (1Password) CLI installed and authenticated, as the skill relies on locally stored tokens for secure registry authentication.

Use Cases

• Production Releases: Use this when a PR is merged into the main branch and a stable version increase is required (patch, minor, or major).
• Documentation Synchronization: Automatically update your SKILL.md files during the build process to ensure that external users always see the correct version metadata.
• Previewing Changes: Execute releases in --dry-run mode to verify that the logic correctly identifies the next version and confirms which files will be modified before making permanent git commits or registry updates.
• Tagging Only: Utilize the --no-publish flag when you need to maintain version parity between your local code and remote git tags without triggering automated registry deployment.

Example Prompts

1. "Perform a patch release for the current repo and include the note 'Fix typo in README'."
2. "Run a minor version bump as a dry run to see what the changelog update will look like."
3. "Release a major version, skipping the npm publication step but updating the git tags."

Tips & Limitations

• YAML Frontmatter: This tool exclusively updates the version: field in SKILL.md when it is wrapped in YAML frontmatter markers (---). If your file lacks this structure, the tool will skip it.
• Security: Ensure your environment has access to the secret store defined in ~/.openclaw/secrets/op-sa-token to avoid authentication failures during the publication phase.
• Git Safety: Always run the tool from the main branch. If you encounter "Push failed" errors, verify that branch protection rules permit the automated agent to push tags and commits.
• Unsupported Workflows: Currently, this skill does not support pre-release, beta, or alpha versioning schemas.