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

Release Process Skill

Automates VS Code extension Marketplace release including versioning, changelog updates, publishing, and PAT setup.

1|1|Updated Nov 20, 2025
Search Tags:#automation#vscode#versioning#release#publish#marketplace#pat
One-click install
npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill release-process-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Release Process Skill
Source: https://github.com/fabioc-aloha/AIRS_Data_Analysis/tree/main/.github/skills/release-process
Command: npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill release-process-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines and automates the entire process of releasing extensions to the VS Code Marketplace, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • End-to-End Automation: Manages version bumping, changelog updates, and publishing.
  • Pre-Release Validation: Includes comprehensive checks before publishing to catch issues early.
  • PAT Management: Provides guidance on Personal Access Token setup and troubleshooting.
  • Use Case: When you're ready to release a new version of your VS Code extension, this Skill can handle the entire deployment pipeline, from updating version numbers to publishing the final package.

Quick Start

Use the release process skill to publish a patch version of the VS Code extension.

Frequently Asked Questions about Release Process Skill

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

FAQPage Schema
How do I automate VS Code extension publishing to the Marketplace?▼

Automate VS Code extension publishing by using a release process that handles version bumping, updates changelogs, and deploys the package to the Marketplace. This reduces manual errors and ensures consistent deployments.

What is a preflight check for VS Code extension releases?▼

A preflight check for extension releases validates release criteria before publishing to the Marketplace. It catches issues early by ensuring synchronization across multiple project files and verifying configurations.

How do I set up a Personal Access Token for VS Code Marketplace publishing?▼

Set up a Personal Access Token (PAT) for Marketplace publishing by configuring it within your release process environment. The release process provides guidance on PAT setup and troubleshooting authentication issues.

Can I synchronize version numbers across multiple project files during a release?▼

Yes, you can synchronize version numbers across multiple project files during a release. The release process ensures synchronization across project files while managing version bumping and changelog updates.

Why does my VS Code extension release fail authentication?▼

Extension release authentication fails due to Personal Access Token (PAT) misconfiguration. The release process manages PAT setup and troubleshooting to resolve authentication errors during Marketplace publishing.

Related Skills

Explore More Software Engineering Skills→
sergeyitalysergeyitaly
1

vscode-extension-publishing

Automate building, packaging, and publishing VS Code extensions to the Marketplace.

Community
Intermediate
klaudworksklaudworks
181

npm-publisher

Automate npm package releases with version bumps, Git tags, and CI/CD publishing.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
Roeia1Roeia1
13

publish

Automate SAGA releases by bumping versions, updating changelogs, and publishing artifacts.

Community
Advanced