taglisted

# Git Tag — SemVer release skill Creates a SemVer annotated tag on `main` by reading conventional commits since the last tag, inferring the correct bump (major / minor / patch), showing a full proposal for approval, then tagging, pushing, and optionally opening a GitHub Release. Never tags silently — the user always approves the version first. ## Accepted flags (parsed from the user's invocation text) | Flag | Effect | |---|---| | `--major` | Force a major bump regardless of commit types | | `--minor` | Force a minor bump regardless of commit types | | `--patch` | Force a patch bump regardless of commit types | | `--pre <suffix>` | Append a pre-release suffix (e.g. `--pre rc.1` → `v1.3.0-rc.1`) | | `--release` | Create a GitHub Release after pushing without prompting | | `--no-release` | Skip GitHub Release creation entirely without prompting | | `--draft` | Create the GitHub Release as a draft (implies `--release`) | | `--no-push` | Create the tag locally only; do not push to the remote | If the user provides a bare version string in the invocation (e.g. `$tag v2.0.0`), use it verbatim and skip bump inference entirely. ## Procedure ### 1. Parse flags and version hint Extract all flags above from the invocation text. If a string matching `v?\d+\.\d+\.\d+` (with an optional pre-release suffix) is present, treat it as an explicit version override and jump to step 6 after confirming it does not already exist. ### 2. Pre-flight checks (run in parallel) - `git fetch --tags