release

Automates Rocket Chat deploys and simplifies complex commands for non-technical users.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iVintik/claude-plugin-ops --skill release-ivintik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/iVintik/claude-plugin-ops/tree/main/skills/release
Command: npx skills add https://github.com/iVintik/claude-plugin-ops --skill release-ivintik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the error-prone manual steps required to release a Claude Code plugin by performing a version bump, committing changes, pushing to the remote, and creating a git tag so CI can propagate the release to marketplaces.

Core Features & Use Cases

  • Version suggestion and bump: Suggests next semver options and applies the chosen version.
  • Atomic git operations: Commits, pushes, and optionally creates tags to trigger CI-driven marketplace updates.
  • Safety flags and guidance: Supports dry-run and no-tag modes, surfaces update commands for manual execution, and warns against running in-session install/update commands that hang.
  • Use case: Use this when you want to ship a new plugin version from a repository containing a .claude-plugin directory and ensure CI and marketplaces are updated consistently.

Quick Start

Release the plugin in the current directory to version 1.2.0 using the release skill with a dry-run if you want to preview changes first.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git tag creation and version bumps for plugin releases?

Automating git tag creation and version bumps for plugin releases involves running a repository's release script to apply semver updates, commit changes, push to the remote, and create tags. This triggers CI-driven marketplace updates automatically.

What's the best way to preview a version bump before publishing a plugin?

To preview a version bump before publishing a plugin, execute the release workflow using the --dry-run flag. This simulates the version update, commit, push, and tag creation process without applying actual changes to the repository.

How does automated release workflow handle CI-driven marketplace updates?

Automated release workflows handle CI-driven marketplace updates by performing atomic git operations. After committing and pushing version bumps, the workflow creates a git tag which triggers the continuous integration pipeline to propagate the release.

Can I push a version bump without creating a git tag?

Yes, you can push a version bump without creating a git tag by using the --no-tag flag. This performs the version update, commit, and push operations while skipping tag creation, allowing manual control over CI triggers.

Why does running in-session plugin install commands hang during release?

Running in-session plugin install commands hang during release because the automated workflow explicitly prevents their execution. The release skill surfaces update commands for manual execution outside the session to avoid process deadlocks.

Does the automated release workflow require a specific directory structure?

Yes, the automated release workflow requires a specific directory structure. It applies exclusively to projects containing a .claude-plugin directory to ensure the release script can correctly identify and package the plugin for publishing.