What problem does it solve? Turning an exact Git commit into a formal, externally observable release is error-prone: tags get misplaced, GitHub Releases drift from their tags, partial publications are hard to resume, and version numbers get chosen without evidence. This Skill provides a deterministic, fail-closed Commit -> Release workflow with dry-run planning, idempotent recovery, and machine-readable verification. ## Core Features & Use Cases - Deterministic release planning: Inspect a target commit, classify SemVer impact from evidence, and produce a sealed JSON dry-run plan before any remote mutation. - Fail-closed publication: Create the annotated tag first, push without force, create a draft GitHub Release, upload and verify artifacts/provenance, then publish and re-verify. - Idempotent recovery and verification: Resume correct partial states (tag-only or matching draft), reject inconsistent tag/release identity, and resolve version -> tag -> exact SHA for downstream automation. - Use Case: You need to cut release v1.7.0 from a specific commit on a maintenance branch. Run inspect and plan to review the exact operations, then publish the reviewed plan and resolve the release as JSON for your CI/CD pipeline. ## Quick Start Ask the agent to dry-run and then publish a GitHub release for a specific commit using the coferlandia-release script with an explicit SemVer version, title, and release notes file.
