plugin-release-hygiene

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.

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.

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.

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.

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.

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.