claude-code-plugin-release

Execute plugin release workflows with version bumping, npm publishing, and documentation updates.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/liujiayi3703/scientific-research-skills --skill claude-code-plugin-release-liujiayi3703
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-plugin-release
Source: https://github.com/liujiayi3703/scientific-research-skills/tree/main/library/skills/version-bump
Command: npx skills add https://github.com/liujiayi3703/scientific-research-skills --skill claude-code-plugin-release-liujiayi3703

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, git, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the complex task of releasing and versioning an AI agent plugin/package across multiple environments and platforms, simplifying the process of semantic versioning, packaging, publishing, and documentation management.

Core Features & Use Cases

  • Version Bumping: Automates version incrementation for release management across various manifest files.
  • Environment Setup: Identifies repository details and specifies paths where version strings are stored.
  • Build & Sync: Ensures artifacts are built, synchronized, and platforms are ready for use.
  • Git Integration: Manages commits, tags, and pushes to both local and remote repositories.
  • Publishing: Handles package publication on npm for global accessibility.
  • Documentation Updates: Automatically updates release notes and changelogs.

Quick Start

Run 'claude-code-plugin-release' to initiate the release process for your plugin.

Frequently Asked Questions about claude-code-plugin-release

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

FAQPage Schema
How do I automate npm plugin release and version management across multiple manifest files?

To automate plugin release, this Skill executes a comprehensive workflow that increments semantic versions and synchronizes package.json, marketplace.json, and plugin.json files to ensure absolute consistency across your release artifacts.

What is the best way to manage git commits and tags during a plugin packaging workflow?

Managing git integration during plugin packaging is handled automatically by creating version commits, applying corresponding tags, and pushing changes directly to both local and remote repositories to finalize the release.

How does version bumping work for npm packages when publishing a new release?

Version bumping works by identifying repository details and specified paths where version strings are stored, automatically incrementing the semantic version across all necessary manifest files before executing the npm publication.

Do I need local build environments and GitHub access to automate my plugin release?

Yes, you need local build environments, GitHub, and npm access to use this release workflow, as it requires local artifact regeneration and repository synchronization to successfully execute the publication process.

Can I automatically update release notes and changelogs when publishing an npm package?

Yes, you can automatically update release notes and changelogs during the npm package publication process, as the workflow includes dedicated documentation management to generate and sync release details.

Why are my plugin manifest files out of sync after a version increment?

Plugin manifest files like package.json, marketplace.json, and plugin.json fall out of sync when version bumping is done manually, which this Skill prevents by automatically applying the version increment across all configured paths simultaneously.