git-wrapup

To create a Git tag for a release commit locally, this Skill wraps working-tree changes into a single conventional commit and applies an annotated v<version> tag without pushing or publishing.

Yes, the release tagging process enforces a verification gate by running devcheck and test:all before committing, preventing broken or half-finished edits from becoming a release.

Yes, you can update version numbers across multiple project files during a release, as this Skill propagates version bumps across package manifests, server manifests, badges, and pinned docs.

The best way to prevent untracked changes from ending up in a versioned release is using strict pre-gate checks that verify the working tree before generating a release commit and annotated Git tag.

To generate a changelog entry when bumping a project version, this Skill authors a per-version changelog entry and regenerates rollups and structural docs to maintain repository consistency.

A limitation of a local-only workflow for release tagging is that it creates commits and annotated tags strictly on the local machine, meaning no push or publish to a remote repository occurs automatically.