skills.rest
aussiegingersnap
aussiegingersnapCOMMUNITY
Explore all skills by this author →
𝕏@jasontoevsGitHub

versioning

Automate semantic versioning and changelog generation for Node.js projects using conventional commits.

9|2|Updated Jan 31, 2026
Search Tags:#changelog#versioning#release-management#semantic-versioning#conventional-commits#git-tags
One-click install
npx skills add https://github.com/aussiegingersnap/cursor-skills --skill versioning-aussiegingersnap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/aussiegingersnap/cursor-skills/tree/main/skills/versioning
Command: npx skills add https://github.com/aussiegingersnap/cursor-skills --skill versioning-aussiegingersnap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic versioning and changelog maintenance are error-prone and time-consuming during releases; this skill automates version bumps, changelog generation, and git tagging based on conventional commits.

Core Features & Use Cases

  • Automates version bumps based on conventional commits
  • Generates CHANGELOG.md using standard-version
  • Tags git with semantic versions
  • Supports monorepos and multi-package setups

Quick Start

Run the release process in your Node project to generate a new version and changelog.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I automate semantic versioning and changelog generation from conventional commits?▼

Automate semantic versioning by running a release process that parses conventional commits to determine version bumps, generates a CHANGELOG.md using standard-version, and applies git tags automatically in your Node project.

Can I coordinate release workflows and version bumps for a monorepo?▼

Yes, release workflows support monorepos and multi-package setups to coordinate version bumps across packages, generate changelogs, and apply git tags based on conventional commit history.

What is the best way to maintain a changelog using standard-version in a Node project?▼

The best way to maintain a changelog is using standard-version to automatically generate CHANGELOG.md entries by analyzing conventional commits during the release workflow in your Node project.

Do I need conventional commits to automate git tagging with semantic versions?▼

Yes, conventional commits are required to automate git tagging with semantic versions, as the commit message format determines the correct version bump level for the release workflow.

Why does automated semantic versioning require a package.json file?▼

Automated semantic versioning requires a package.json file because the release workflow updates the version field in this Node project manifest before generating the changelog and applying git tags.

What are the limitations of using standard-version for changelog management?▼

A limitation of standard-version for changelog management is that it strictly requires conventional commit compliance and a Node project setup, meaning non-conventional commit histories will not produce accurate version bumps or changelog entries.

Related Skills

Explore More Software Engineering Skills→
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
crmagzcrmagz
6

package-management

Coordinate CDK package metadata, dependencies, and workspace references across monorepo subpackages.

Community
Intermediate
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced