plugin-release-hygiene

Name: plugin-release-hygiene
Availability: InStock
Author: grimblaz

Propose semantic version bumps for plugin entry-point edits.

3|Updated Dec 7, 2025

Search Tags:#audit #plugin #release #claude-code #hook #copilot #version-bump

Ready to run

npx skills add https://github.com/Grimblaz/agent-orchestra --skill plugin-release-hygiene

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-release-hygiene
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/plugin-release-hygiene
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill plugin-release-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, powershell, and includes scripts (resource) components.

What problem does it solve?

Maintainer-side guardrails prevent shipping plugin-entry edits without a version bump, ensuring an explicit Claude/Copilot update surface and a clear audit trail for changes.

Core Features & Use Cases

Deterministic release hygiene: proposes a version bump (patch by default, with optional minor/major overrides) when entry-point edits touch agents, commands, skills, or root plugin.json, and records touched paths for audit.
Cross-platform surface: integrates with Claude Code and Copilot workflows via PostToolUse hooks to surface the bump decision to maintainers.
Stateful review: persists per-conversation state to coalesce multiple edits into a single release decision and avoid repeated prompts.

Quick Start

Enable the plugin-release-hygiene hook so that entry-point edits trigger a version-bump proposal before shipping.

Frequently Asked Questions about plugin-release-hygiene

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

FAQPage Schema

How do I automate semantic version bumps for plugin entry-point edits in Claude Code?▼

Semantic version bumps for plugin entry-point edits are automated by proposing a default patch increment, with optional minor or major overrides, when changes touch agents, commands, skills, or root plugin.json. Touched paths are recorded to support auditability and rollback.

Why do my plugin release edits ship without a clear audit trail for Claude or Copilot?▼

Shipping plugin release edits without an audit trail occurs because maintainer-side guardrails are missing. Applying a PostToolUse hook surfaces the version-bump decision and records touched paths, ensuring a controlled release and explicit audit trail for Claude and Copilot workflows.

Can I use a PostToolUse hook to coalesce multiple plugin.json edits into a single release decision?▼

Yes, a PostToolUse hook can coalesce multiple plugin.json edits into a single release decision. The process persists per-conversation state to group entry-point changes across agents, commands, and skills, avoiding repeated prompts before shipping.

How do I prevent shipping changes to plugin agents and commands without incrementing the version?▼

To prevent shipping changes to plugin agents and commands without a version increment, enable a release hygiene hook. It proposes a semantic version bump, defaulting to patch, whenever entry-point edits are detected, ensuring controlled release management.

Does the plugin release hygiene hook require git and powershell to run?▼

Yes, the plugin release hygiene hook requires both git and powershell dependencies to function. These tools provide the necessary environment for executing the scripts that track entry-point edits and apply version bumps.

What is the default version bump applied when modifying root plugin.json?▼

The default version bump applied when modifying root plugin.json or other entry-point areas is a patch increment. This default can be overridden with a minor or major bump depending on the scope of the release changes.