cut-release

Authors release notes and publishes Fabrik releases via a guarded shell script.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill cut-release-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cut-release
Source: https://github.com/handarbeit/fabrik/tree/main/.claude/skills/cut-release
Command: npx skills add https://github.com/handarbeit/fabrik --skill cut-release-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about cut-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cut a new Fabrik release?

Invoke /cut-release with an optional version like v0.0.67. The skill gathers commits since the last tag, writes release notes to release-notes/<version>.md, then runs scripts/cut-release.sh to commit, tag, push, and verify the release.

How are Fabrik release notes generated?

The skill runs git log from the last tag to HEAD, groups user-facing commits into Features, Fixes, Improvements, and Internal sections, and writes them to release-notes/<version>.md with a required heading and Summary section.

Can anyone use the cut-release script to publish?

No. The script is bot-only: it reads FABRIK_TOKEN from .env and aborts unless gh api user resolves to @arbeithand. Fork maintainers would need to parameterize the constants at the top of the script.

Why does the release publish with the wrong author identity?

Wrong-identity attribution is caused by the PUBLIC_REPO_RELEASE_TOKEN repo secret used by the release workflow. The script verifies release.author.login and Discussion author after publishing and aborts loudly if either is not arbeithand.

What happens if the cut-release script fails partway through?

The script avoids destructive cleanup and exits non-zero with an error message. The skill surfaces that error verbatim and relays the commented cleanup commands at the bottom of the script rather than attempting automatic repair.