publish

Name: publish
Availability: InStock
Author: RoeiA

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

13|1|Updated Nov 21, 2025

Search Tags:#automation #git #changelog #versioning #npm #github #release

Ready to run

npx skills add https://github.com/Roeia1/SAGA --skill publish-roeia1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/Roeia1/SAGA/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/Roeia1/SAGA --skill publish-roeia1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release workflow for SAGA by coordinating version bumps, changelog updates, and publishing artifacts across both the Claude Code plugin and the dashboard package.

Core Features & Use Cases

Automated version bumps across plugin and dashboard to keep them in sync.
Changelog generation and formatting for GitHub releases and npm publishing.
End-to-end publishing workflow including Git tagging, GitHub release creation, and npm deployment.

Quick Start

Tell this skill to perform a release by specifying the version bump type (MAJOR, MINOR, or PATCH).

Frequently Asked Questions about publish

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

FAQPage Schema

How do I automate npm publishing and GitHub releases for multiple packages?▼

Automated release workflows handle end-to-end publishing by coordinating Git tagging, GitHub release creation, and npm deployment across multiple packages to keep versions synchronized.

How do I keep version numbers in sync across a plugin and dashboard package?▼

Cross-package version synchronization aligns version numbers across different packages by applying automated version bumps simultaneously during the release process.

How do I generate a changelog and format it for a GitHub release?▼

Changelog generation automates updating and formatting changelog content specifically for GitHub releases and npm publishing to maintain release documentation integrity.

Do I need to specify the version bump type to start an automated release?▼

Yes, you need to specify the version bump type as MAJOR, MINOR, or PATCH to initiate the automated release workflow and apply the correct version increments.

What's the best way to manage end-to-end release workflows for npm packages?▼

End-to-end release workflows manage version bumps, changelog updates, Git tagging, and npm publishing in a coordinated process to ensure release consistency across packages.

Why does cross-package version alignment matter for plugin and dashboard releases?▼

Cross-package version alignment ensures the plugin and dashboard packages remain compatible during deployment, preventing version mismatches that can break integrated functionality.