skills.rest
zotoio
zotoioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

xfi-release-workflow

Coordinate synchronized multi-package releases for X-Fidelity CLI and VSCode extension.

1|1|Updated Dec 20, 2023
Search Tags:#automation#workflow#versioning#publishing#release#ci-cd#conventional-commits
One-click install
npx skills add https://github.com/zotoio/x-fidelity --skill xfi-release-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xfi-release-workflow
Source: https://github.com/zotoio/x-fidelity/tree/main/.cursor/skills/xfi-release-workflow
Command: npx skills add https://github.com/zotoio/x-fidelity --skill xfi-release-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing X-Fidelity across the CLI and VSCode extension is complex without a unified, repeatable process. This skill codifies the end-to-end release workflow to ensure version synchronization, changelog generation, and automated publishing.

Core Features & Use Cases

  • Unified release orchestration: coordinates version bumps, changelog updates, builds, and publishing for both packages.
  • Conventional-commit driven: supports standard commit types to drive release cadence and prerelease handling.
  • Post-release verification: provides dry-run options and guidance for validating npm, VSCode marketplace, and Open VSX publishing.

Quick Start

Run the unified release workflow from the repository root to perform a dry-run or a full local release using the configured environment variables.

Frequently Asked Questions about xfi-release-workflow

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

FAQPage Schema
How do I synchronize version bumps for a CLI tool and a VSCode extension during a release?▼

A multi-package release workflow synchronizes versions by coordinating version bumps, builds, and publishing across both the CLI and VSCode extension simultaneously to ensure aligned release cycles.

How do conventional commits drive automated publishing and prerelease versions?▼

Conventional commits drive automated publishing by using standard commit types to determine release cadence and prerelease handling, automatically generating changelog updates and version bumps.

Can I run a dry-run release to validate npm, VSCode marketplace, and Open VSX publishing?▼

Yes, you can perform a dry-run release from the repository root to validate package builds and verify publishing configurations for npm, VSCode marketplace, and Open VSX before executing a full release.

What environment variables are required for CI environment release automation?▼

CI environment release automation requires configured environment variables for npm and VSCode marketplace authentication, which the workflow encodes to ensure successful publishing and post-release verification.

What is the best way to troubleshoot version synchronization issues across local and CI environments?▼

Troubleshoot version synchronization by executing the codified release workflow steps and post-release verification checks, ensuring repeatable version alignment and changelog generation across local and CI environments.

Related Skills

Explore More Software Engineering Skills→
shirulotshirulot

changelog-automation

Parse commit history to generate changelogs and release notes.

Community
Advanced
sergeyitalysergeyitaly
1

cursor-kiro-extension-publishing

Publish VS Code extension VSIX files to Open VSX for Cursor and Kiro IDEs.

Community
Intermediate
GuidoBergmanGuidoBergman

testarch-ci

Scaffold a CI/CD quality pipeline with test execution, burn-in loops, and artifact collection.

Community
Advanced
nickm538nickm538

github-release-management

Coordinate versioning, changelogs, builds, and deployments for GitHub releases.

Community
Advanced