What problem does it solve? Cutting a Fabrik release involves many error-prone steps — gathering commits since the last tag, writing categorized release notes, tagging, pushing as the correct bot identity, and verifying the release workflow. This Skill automates the orchestration so releases are published consistently and attributed to the correct bot account. ## Core Features & Use Cases - Release notes authoring: Enumerates commits since the last tag, groups them into Features, Fixes, Improvements, and Internal sections, and writes them to release-notes/<version>.md following a strict schema with a required Summary block. - Guarded publication: Delegates commit, tag, push, workflow watching, and identity verification to scripts/cut-release.sh, which enforces pre-flight checks, PAT identity validation, and post-publish author verification. - Use Case: After merging several features into main, invoke /cut-release v0.0.67 to generate the release notes, publish the GitHub Release as @arbeithand, and automatically file the doc-update issue on the project board. ## Quick Start Ask the assistant to cut a new Fabrik release, optionally specifying a version like v0.0.67, and it will draft the release notes and run the publish script.