skills.rest
jimeh
jimehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

hucode-bump-version

Bumps Hucode release version and updates changelog from change fragments.

Updated Apr 14, 2026
Search Tags:#changelog#release#release automation#semver#version bump#hucode
One-click install
npx skills add https://github.com/jimeh/hucode --skill hucode-bump-version-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hucode-bump-version
Source: https://github.com/jimeh/hucode/tree/main/.agents/skills/hucode-bump-version
Command: npx skills add https://github.com/jimeh/hucode --skill hucode-bump-version-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a Hucode release requires coordinated edits across product.json, CHANGELOG.md, and .changes fragments; doing this by hand risks inconsistent version metadata and stale changelog entries. ## Core Features & Use Cases - Fragment-Backed Releases: Runs the hucode:prepare-release helper to consume .changes fragments, update CHANGELOG.md with the new version section, and bump hucodeVersion in build/hucode/mixin/stable/product.json. - Metadata-Only Bumps: Handles explicit version-only bumps when no change fragments exist, editing only hucodeVersion and running prepare, validate, and precommit checks. - Release Commit Guidance: Produces the conventional commit subject "chore(release): bump Hucode to <version>" scoped to the release artifacts. - Use Case: After merging feature work with .changes fragments, ask for a patch release and get a validated diff covering the changelog entry, version bump, and deleted fragments. ## Quick Start Use the hucode-bump-version skill to bump Hucode to the next patch version and prepare the release metadata.

Frequently Asked Questions about hucode-bump-version

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

FAQPage Schema
How do I bump the Hucode release version?▼

Run npm run hucode:prepare-release -- --version <target-version> when .changes fragments exist, then run hucode:prepare and hucode:validate. This updates hucodeVersion in build/hucode/mixin/stable/product.json and adds the changelog section.

How do I prepare a Hucode release from .changes fragments?▼

The hucode:prepare-release helper consumes .changes markdown fragments, generates the new CHANGELOG.md section with today's date, deletes the consumed fragments, and bumps hucodeVersion. Follow with targeted precommit hygiene on the changed files.

Should I bump the root package.json version for a Hucode release?▼

No. Root package.json and root product.json stay on the upstream VS Code compatibility line. Only hucodeVersion in build/hucode/mixin/stable/product.json changes for a Hucode release.

What happens if no .changes fragments exist for a release?▼

The skill pauses and asks whether you want a metadata-only bump or whether a fragment is missing. A metadata-only bump edits only hucodeVersion and does not generate a changelog entry.

Why does hucode:prepare-release fail with a missing @commitlint/parse package?▼

This happens when node_modules are incomplete. Run npm install, re-check git status, then retry the prepare-release command without widening the release diff.

Related Skills

Explore More Software Engineering Skills→
dahliadahlia
2.0k

sacho

Manages changelogs as Markdown fragments compiled into CHANGES.md at release time.

Community
Intermediate
drvossdrvoss
42

release

Automates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.

Community
Advanced
OliverOuyangOliverOuyang
1

release

Automate version bumps, tests, git tags, npm publish, and GitHub releases for oh-my-claudecode.

Community
Advanced
jonaseck2jonaseck2
2

oss-release

Enforce CHANGELOG.md release-note structure with a 10-block rolling window.

Community
Intermediate