Stats
Actions
Tags
From principled-release
Tag and finalize a release. Validates the tag, verifies release readiness, generates changelog and release notes, creates the git tag, and optionally creates a GitHub release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/principled-release:tag-releaseThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate, tag, and finalize a release with generated release notes. This is the final orchestration step that brings together readiness verification, changelog generation, and tag creation.
Validate, tag, and finalize a release with generated release notes. This is the final orchestration step that brings together readiness verification, changelog generation, and tag creation.
/tag-release <version> [--dry-run]
| Argument | Required | Description |
|---|---|---|
<version> | Yes | The version to tag (e.g., 0.4.0 or v0.4.0) |
--dry-run | No | Show what would happen without creating the tag |
gh CLI required for GitHub release creation (optional for tag-only)Validate the tag. Check format and uniqueness:
bash scripts/validate-tag.sh <version>
Ensures the version follows semver format and the tag doesn't already exist.
Check working tree. Verify no uncommitted changes:
git status --porcelain
If the working tree is dirty, warn the user and ask to commit or stash first.
Verify release readiness. Run the strict readiness check:
bash ../release-ready/scripts/check-readiness.sh --since <previous-tag> --strict
If any referenced pipeline document is not in terminal status, report the failures and stop (unless --dry-run).
Determine the previous tag. Find the most recent tag for changelog scope:
git describe --tags --abbrev=0
Generate changelog. Collect and format changes since the previous tag:
bash ../changelog/scripts/collect-changes.sh --since <previous-tag>
Format the output into release notes using the changelog template.
In dry-run mode, report and stop. If --dry-run is set:
Dry run for v0.4.0:
Previous tag: v0.3.1
Commits since: 23
Readiness: PASS (5/5 documents in terminal status)
Changelog: 8 entries (2 features, 3 improvements, 2 decisions, 1 uncategorized)
Would create:
- Git tag: v0.4.0
- Release notes with changelog
Stop without creating anything.
Create the git tag. Tag the current commit:
git tag -a v<version> -m "Release v<version>"
Create GitHub release (optional). If gh is available, create a GitHub release:
gh release create v<version> --title "v<version>" --notes "<release-notes>"
Report results.
Release v0.4.0 created:
Tag: v0.4.0
Commits: 23 since v0.3.1
Changelog: 8 entries
GitHub release: https://github.com/owner/repo/releases/tag/v0.4.0
scripts/check-gh-cli.sh --- Verify gh CLI availability and auth status (copy from principled-github canonical)scripts/validate-tag.sh --- Validate tag format and check for duplicatesnpx claudepluginhub alexnodeland/principled --plugin principled-releaseValidates and executes software releases with changelog generation, version bumping, git tagging, and CI verification.
Cuts annotated semver tags with release notes derived from recent commits. Validates version, notes, and files before tagging.
Creates a GitHub release with semantic versioning, changelog generation, release notes, and optional build artifacts via tags and GitHub CLI.