skill-repository-versioning

Classify the pending change, bump each modified skill's own metadata.version, update the skill index if inventory changed, run the mechanical validator, then decide whether the installable surface changed enough to warrant a repo-wide release bump with release notes.

Bump the repo-wide release version when the installable surface changes: a skill added, removed, or deprecated, or manifest, packaging, or shared protocol changes. A content-only edit to one skill only requires that skill's own version bump.

No, it defers. If the target repository provides a local release skill under .agents/skills/ that owns versioning, manifests, or release readiness, this generic workflow stops and hands off to the repository-specific policy.

Mechanical validators check each skill's frontmatter but not whether the index matches reality. Updating the index after adding, removing, or renaming a skill is a manual step that is commonly forgotten.

It assumes a specific repository layout with a skill index, per-skill metadata.version, validator scripts, and a version-bump config. Missing pieces are treated as not applicable, and it does not write commit messages — that belongs to the repo's dev-process skill.