What problem does it solve? Coordinating a multi-package Haskell release is error-prone: versions, internal dependency bounds, changelogs, per-package git tags, Hackage uploads, and GitHub releases must all stay in lockstep, and a single missed bound or out-of-order upload ships a broken package. This Skill encodes the entire keiro release procedure as a gated, reviewable workflow. ## Core Features & Use Cases - PVP version management: Infers or accepts a major/minor/patch bump, updates all seven cabal files, and aligns internal dependency bounds discovered by scanning manifests rather than trusting memory. - Mandatory verification gates: Runs nix fmt, corpus regeneration, just verify, and nix flake check before any commit, with documented handling for known failure modes like conformance provenance restamping. - Ordered Hackage publishing: Uploads packages in dependency order (keiro-core through keiro-ops) with cabal check, sdist, documentation builds, and post-upload liveness verification, stopping on any failure. - Use Case: After merging a cycle of changes to the keiro event-sourcing framework, invoke the skill with a patch argument to bump 0.14.0.0 to 0.14.0.1, regenerate changelogs, tag all seven packages, and publish them to Hackage with a GitHub release. ## Quick Start Ask the assistant to run the release skill with a patch argument to cut and publish the next keiro release.