release-publishing-workflow

Automate version bumps, CHANGELOG updates, npm publishing, and git tagging for a multi-package MCP monorepo.

Updated Oct 1, 2025
One-click install
npx skills add https://github.com/j0KZ/mcp-agents --skill release-publishing-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-publishing-workflow
Source: https://github.com/j0KZ/mcp-agents/tree/main/starter-kit/template/.claude/skills/release-publishing-workflow
Command: npx skills add https://github.com/j0KZ/mcp-agents --skill release-publishing-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complete release workflow for a multi-package monorepo, handling version bumps, CHANGELOG management, npm publishing, git tagging, and deployment verification to reduce manual toil and risk during releases.

Core Features & Use Cases

  • Version Management: Sync and publish versions across all packages in the monorepo.
  • CHANGELOG Automation: Maintain accurate release notes and history.
  • End-to-End Publishing: Publish all packages to npm with a single workflow, including verification of deployment.
  • Git Tagging & Release: Create and push git tags for traceability.
  • Deployment Verification: Validate deployments across platforms post-release.
  • Emergency Hotfix Support: Streamlined rollback and hotfix release steps.

Quick Start

Update to a new version, then run through the automated release steps: update version.json, run version synchronization, update CHANGELOG.md, commit changes, publish all packages, create a git tag, push to GitHub, and verify deployments. Reference the complete-release-checklist for the full process.

Frequently Asked Questions about release-publishing-workflow

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

FAQPage Schema
How do I automate version bumps and publishing across multiple npm packages?

Automating version bumps and publishing across packages uses a centralized version file (version.json) to sync versions, then runs automated workflows to update CHANGELOGs, publish all packages to npm, create git tags, and verify deployments—eliminating manual coordination and reducing release errors.

What's the best way to manage CHANGELOG updates during multi-package releases?

CHANGELOG automation templates and maintains release notes across all packages in the monorepo, ensuring consistent documentation, accurate version history, and traceability without manual editing for each package.

Can I publish all packages in a monorepo to npm in a single workflow?

Yes, end-to-end publishing handles all packages to npm simultaneously with built-in deployment verification across platforms, reducing the risk of partial releases and ensuring consistency.

How do I handle emergency hotfixes and rollbacks in a multi-package monorepo?

Emergency hotfix support provides streamlined rollback and hotfix release steps that maintain version consistency across packages while minimizing downtime and manual intervention.

What git tagging and release traceability does a monorepo workflow need?

Git tagging creates and pushes tags for each release, providing version traceability, deployment history, and rollback reference points across the entire monorepo.