Automate release governance with version stamping, changelog updates, and CI validation.
npx skills add https://github.com/usurobor/cnos --skill release-usurobor
Please help me install this Agent Skill. Skill: release Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/release Command: npx skills add https://github.com/usurobor/cnos --skill release-usurobor
This Skill provides end-to-end governance for software releases, ensuring that each release is a coherent delta with a matching code state, changelog, tag, release notes, deployment, and validation.
Run the release workflow from the main branch to stamp VERSION, update CHANGELOG, generate RELEASE.md, tag the release, and wait for CI completion.
High-intent search queries and answers about installing and using this skill.
Automated release governance bumps the VERSION file, runs stamp-versions.sh, verifies consistency across manifests, and updates the CHANGELOG ledger to produce a coherent code delta. It enforces version consistency checks before tagging.
A measured coherence delta is a release state where code, changelog, tag, release notes, deployment, and validation all match. End-to-end release governance enforces this consistency to ensure artifacts align across all surfaces.
Pre-release readiness checks verify CI is green, branches are merged, and main is clean before tagging. The release workflow enforces these gating checks to ensure the codebase is stable and validated before version stamping occurs.
No external dependencies are required. The workflow coordinates with existing CI validation by triggering release pipelines and waiting for completion, but operates independently to manage tagging, deployment, and post-release assessment.
Release documentation generates a RELEASE.md file and updates CDD traces to maintain release artifacts. It ensures artifact traceability and compliance by verifying that binaries match across all deployment surfaces after validation.
Delta release tagging occurs after CI completion on main or release branches. You should coordinate with delta reviewers to create annotated tags only when pre-release checks pass and validated binaries are ready for deployment.
cacr92Merge the current Git branch into main and prune all other branches.
usuroborAutomate post-release evaluation and write assessment artifacts to docs/gamma/cdd/{X.Y.Z}/POST-RELEASE-ASSESSMENT.md.
max-sixtyAutomate Worktrunk releases with testing, version bumps, changelog updates, and tagging.
hrygoAutomate HotPlex releases with version bumps, changelogs, and unified component versions.
