skills.rest
fabioc-aloha
fabioc-alohaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

extension-versioning

Manage semantic versioning and CHANGELOG formatting for VS Code extensions.

Updated Feb 24, 2026
Search Tags:#changelog#release management#versioning#npm#semver#vscode extensions
One-click install
npx skills add https://github.com/fabioc-aloha/Extensions --skill extension-versioning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extension-versioning
Source: https://github.com/fabioc-aloha/Extensions/tree/main/.github/skills/extension-versioning
Command: npx skills add https://github.com/fabioc-aloha/Extensions --skill extension-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing versions for VS Code extensions, ensuring consistency and adherence to semantic versioning standards.

Core Features & Use Cases

  • Semantic Versioning: Guides on applying patch, minor, and major version bumps.
  • Changelog Management: Enforces the Keep a Changelog format for clear release notes.
  • Release Cadence: Provides recommendations for publishing frequency based on extension priority.
  • Use Case: When preparing to release a new feature for your VS Code extension, use this Skill to determine the correct version bump, update the CHANGELOG.md, and follow the recommended release process.

Quick Start

Use the extension versioning skill to bump the patch version of the hook-studio extension.

Frequently Asked Questions about extension-versioning

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

FAQPage Schema
How do I manage semantic versioning for multiple VS Code extensions in a single repository?▼

You manage semantic versioning by applying deterministic version updates, ensuring consistent patch, minor, and major version bumps across all extensions within a repository. This standardizes release notes and maintains version synchronization.

What is the best way to format a CHANGELOG.md for a VS Code extension release?▼

The best way to format a CHANGELOG.md is by adhering to the Keep a Changelog standard. This enforces clear, structured release notes that document patch, minor, and major version bumps for your extension.

When do I need to use a pre-release channel for VS Code extension versioning?▼

You need a pre-release channel for VS Code extension versioning when preparing features for gradual rollout. Pre-release channel management isolates in-development changes from stable semantic versioning bumps before the final release.

Does this approach support npm version bumping standards for VS Code extensions?▼

Yes, this approach supports npm version bumping standards by guiding the application of semantic versioning for VS Code extensions. It aligns patch, minor, and major version updates with standard npm release cadences.

How do I determine the correct version bump when releasing a new VS Code extension feature?▼

To determine the correct version bump, evaluate your changes against semantic versioning rules: use a minor bump for new features, a patch bump for fixes, and a major bump for breaking changes. This ensures standardized release notes.

Related Skills

Explore More Software Engineering Skills→
jparkerwebjparkerweb
87

ai-assist-changelog-bump

Validate CHANGELOG.md against main and compute semver bumps for package.json.

Community
Intermediate
Sumeet138Sumeet138
1

changelog-automation

Generate release notes and changelogs from commits and PRs.

Community
Advanced
avsmavsm
35

ocaml-npm-publishing

Publish OCaml libraries to npm for browser targets using js_of_ocaml and wasm_of_ocaml.

Community
Advanced
MithrilManMithrilMan

gh-release-package

Automate GitHub package releases by bumping package.json and publishing via the Release workflow.

Community
Advanced