skills.rest
clawperator
clawperatorOFFICIAL
Explore all skills by this author →
GitHub

release-set-code-version-number

Bump unreleased Clawperator code version in Node files with validation and commit.

2|Updated Feb 17, 2026
Search Tags:#automation#git#versioning#release-management#nodejs#build-tests
One-click install
npx skills add https://github.com/clawperator/clawperator --skill release-set-code-version-number
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-set-code-version-number
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/release-set-code-version-number
Command: npx skills add https://github.com/clawperator/clawperator --skill release-set-code-version-number

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Bumps the next unreleased Clawperator code version on code-facing surfaces only, with local validation and an automated commit to keep internal references in sync.

Core Features & Use Cases

  • Automated version bumps: Update code-facing version references in files like apps/node/package.json without altering public release-facing docs.
  • Local validation: Run build and tests to ensure the bump does not break code and maintains integrity.
  • Controlled commits: Create a standardized commit message and preserve a clean git history.
  • Use Case: When preparing a new unreleased version, run the skill to update internal references and validate the change before publishing.

Quick Start

Execute the version-bump script from the repository root with the old and new version numbers to apply the update and commit it automatically.

Frequently Asked Questions about release-set-code-version-number

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

FAQPage Schema
How do I automate version bumps in package.json and commit the changes?▼

Automating version bumps in package.json requires updating code-facing version references and creating a standardized git commit. This skill targets internal files like apps/node/package.json and package-lock.json while excluding public release-facing docs.

What is the best way to update unreleased code versions without breaking tests?▼

The best way to update unreleased code versions safely is by running local validation through npm build and test checks. This skill bumps the version, validates the Node app integrity, and commits only if tests pass.

Does this versioning skill require a clean git working tree to run?▼

Yes, this versioning skill requires a clean git working tree before executing. It enforces this prerequisite to ensure the automated version bump and standardized commit do not conflict with uncommitted local changes.

How do I exclude public release docs when bumping an internal code version?▼

Excluding public release docs when bumping an internal code version is handled automatically by targeting only code-facing surfaces like apps/node/package.json and code tests. The skill leaves release-facing documentation untouched while applying the update.

How does automated release management handle commit messages for version updates?▼

Automated release management handles commit messages by generating a standardized format like chore(build): set code version to <new_version>. This ensures consistent git history when bumping unreleased code versions locally.

Related Skills

Explore More Software Engineering Skills→
deepfuturenowdeepfuturenow

publish-to-npm

Automate version bumps, builds, and npm publishing for @deepfuture packages.

Official
Advanced
dvy1987dvy1987
3

publish-skill

Package and publish validated agent skills to skills.sh and GitHub.

Community
Advanced
48Nauts-Operator48Nauts-Operator
3

git-release

Analyze commits since the last tag and generate release notes.

Community
Intermediate
baekenoughbaekenough
13

omcustom:npm-version

Bump npm package versions and update package.json and CHANGELOG.md.

Community
Advanced