| name | source-command-close-version |
| description | Close the current version in the CHANGELOG ([Unreleased] → [X.Y.Z]) and tag it. |
source-command-close-version
Use this skill when the user asks to run the migrated source command close-version.
Command Template
Close version $ARGUMENTS in docs/CHANGELOG.md.
-
Read docs/CHANGELOG.md. Confirm [Unreleased] has content. If empty, stop and tell the user
there is nothing to release.
-
Rename the ## [Unreleased] heading to ## [$ARGUMENTS] - <today YYYY-MM-DD> and insert a fresh
empty ## [Unreleased] block above it (with placeholder "Add your changes here.").
-
Summarize to the user what is being released.
-
Offer (do NOT run without confirmation) the tag + release commands:
git add docs/CHANGELOG.md
git commit -m "chore(release): v$ARGUMENTS"
git tag v$ARGUMENTS
And, if a GitHub remote exists and gh is available, offer gh release create v$ARGUMENTS.
If ContextDevKit is at Level 5 and a qa gate marker is configured beyond T0, surface any failing
quality signals before closing.