release

Automate Claude Code plugin releases with version bumping and SHA pinning.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/g-bastianelli/nuthouse --skill release-g-bastianelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/g-bastianelli/nuthouse/tree/main/.claude/skills/release
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill release-g-bastianelli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The release Skill solves the problem of releasing plugin changes to installed users by automating version bumping and SHA pinning, ensuring compatibility and visibility of updates.

Core Features & Use Cases

  • Automated Version Bumping: Bumps plugin versions before SHA pins to ensure content changes are visible to users.
  • SHA Pinning: Post-version bump, pin SHAs to update marketplace listings.
  • Pre-Push Verification: Includes tests, linting, and formatting checks to prevent regressions.
  • Commit Handling: Commits are managed by the git-gremlin:commit skill to enforce gate checks.

Quick Start

To initiate a release for all changed plugins, simply type 'release versions'. After merging to 'main', run 'release shas' to finalize the SHA pins.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and SHA pinning for Claude Code plugin releases?

Automating version bumping and SHA pinning for Claude Code plugins requires running 'release versions' to bump versions before pushing, then running 'release shas' after merging to main to finalize SHA pins for marketplace listings.

What does SHA pinning do for plugin updates in a marketplace?

SHA pinning updates marketplace listings with a specific commit hash after a version bump, ensuring installed users receive the exact content changes and functional updates intended for the new plugin release.

Do I need pre-push verification checks before releasing a Claude Code plugin?

Pre-push verification is necessary to prevent regressions during plugin releases. The release process automatically includes tests, linting, and formatting checks to ensure code quality before committing and pushing changes.

Can I use git operations to manage commits during the plugin release process?

Git operations are used to manage plugin metadata and commit handling during releases. Commits are delegated to the git-gremlin:commit skill to enforce gate checks and maintain strict version control standards.

Why are my plugin version changes not visible to installed users after an update?

Plugin version changes may not be visible if SHA pinning is not completed. You must bump the version first, then run 'release shas' after merging to main to update the marketplace listing and push content changes to users.