Stats
Actions
Tags
From principled-release
Verify that all pipeline documents referenced by merged changes are in terminal status. Checks proposals, plans, and ADRs to ensure release readiness before tagging.
How this skill is triggered — by the user, by Claude, or both
Slash command
/principled-release:release-readyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify that all proposals, plans, and ADRs referenced by commits since the last release are in terminal status. A passing check means the release is ready to proceed.
Verify that all proposals, plans, and ADRs referenced by commits since the last release are in terminal status. A passing check means the release is ready to proceed.
/release-ready [--tag <version>] [--since <tag>] [--strict]
| Argument | Required | Description |
|---|---|---|
--tag <version> | No | The version being prepared (for reporting only) |
--since <tag> | No | Git tag to use as starting point. Auto-detects latest if absent |
--strict | No | Treat non-terminal documents as hard failures instead of warnings |
gh CLI recommended for enriched PR reference resolution (optional)Verify prerequisites. Check that gh is available:
bash scripts/check-gh-cli.sh
If not available, proceed with commit-based reference resolution only.
Determine the starting tag. If --since is provided, use it. Otherwise, find the most recent tag:
git describe --tags --abbrev=0
Check readiness. Run the readiness checker:
bash scripts/check-readiness.sh --since <tag> [--strict]
This collects all pipeline references from commits since the tag and checks each referenced document's frontmatter status.
Evaluate terminal status. For each referenced document:
accepted, rejected, or superseded = terminalcomplete or abandoned = terminalaccepted, deprecated, or superseded = terminalDocuments in non-terminal status (draft proposals, active plans, proposed ADRs) are flagged.
Report results. Output a structured readiness report:
Release Readiness Check (since v0.3.1):
PASS proposal RFC-001 Principled Docs Plugin accepted
PASS plan Plan-000 Principled Docs Plugin complete
WARN plan Plan-006 Principled Release Plugin active
PASS decision ADR-001 Pure Bash Frontmatter accepted
Summary: 3 passed, 1 warning, 0 failed
In --strict mode, warnings become failures and the skill exits non-zero.
scripts/check-gh-cli.sh --- Verify gh CLI availability and auth status (copy from principled-github canonical)scripts/check-readiness.sh --- Check pipeline document statuses against terminal criterianpx claudepluginhub alexnodeland/principled --plugin principled-releaseValidates and executes software releases with changelog generation, version bumping, git tagging, and CI verification.
Pre-release readiness review that scans for debug artifacts, version mismatches, changelog gaps, git hygiene issues, breaking changes, and license compliance. Runs tests and build verification before presenting consolidated findings for human review.
Validates release readiness via sequential gated checklist: build, tests, security, typecheck, counts, diff review, changelog, version bump, commit, tag, push. Use before release commits.