Interactive release automation tool for versioning and publishing.
Install
mkdir -p .claude/skills/release-openscribbler && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13324" && unzip -o skill.zip -d .claude/skills/release-openscribbler && rm skill.zipInstalls to .claude/skills/release-openscribbler
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate the full release workflow for syllago. USE WHEN creating a release OR tagging a version OR bumping VERSION OR publishing to GitHub releases.Key capabilities
- →Analyze changes since the last release
- →Recommend a version bump based on Semver guidelines
- →Write release notes from a template
- →Create a GitHub Release
- →Bump the `VERSION` string in the codebase
- →Prevent accidental releases with a safety hook
How it works
The skill automates the release workflow by analyzing changes, recommending a Semver version bump, drafting release notes, and publishing to GitHub Releases. It includes human approval steps at decision points and a safety hook to prevent accidental releases.
Inputs & outputs
When to use release
- →Creating a release
- →Tagging a version
- →Publishing to github
About this skill
release
Interactive two-phase release workflow for syllago. Analyzes changes, recommends a version bump, writes release notes, and ships — with human approval at every decision point.
Arguments
No arguments required. The skill determines the version interactively.
Semver Guidelines
Use these criteria when recommending a release type. Present these in the AskUserQuestion options so the user sees the reasoning.
Major (X.0.0)
- Breaking changes to CLI commands (renamed/removed subcommands, changed flags, changed output format)
- Breaking changes to
.syllago.yamlschema that require user migration - Breaking changes to registry protocol or content format
- Dropping support for a provider
- Any change that would break existing scripts or workflows using syllago
Minor (0.X.0)
- New features (commands, subcommands, TUI screens, content types)
- New provider support
- Non-breaking additions to config format or
.syllago.yaml - Significant improvements to existing features (new options, expanded behavior)
- New built-in content (skills, agents, etc.)
Patch (0.0.X)
- Bug fixes
- Performance improvements with no behavior change
- Documentation corrections that ship with the binary (help text, etc.)
- Dependency updates with no user-facing impact
- Minor UX polish (typo fixes, better error messages)
Pre-1.0 Note
While syllago is pre-1.0, minor versions may include small breaking changes if needed. After 1.0, semver is strict — breaking changes require a major bump.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| create-release | /release | workflows/create-release.md |
Flow Overview
/release
1. Analyze changes since last release (git log + diffstat)
2. AskUserQuestion: release type (major/minor/patch) with reasoning
3. Write release notes from template
4. AskUserQuestion: approve release notes
5. Bump VERSION, commit, create .release-pending.yml (status: prepared)
6. AskUserQuestion: ship it?
7. Tag, push, create GitHub Release, delete .release-pending.yml
A safety hook blocks git tag and git push of version tags unless .release-pending.yml exists with status: prepared. This prevents accidental releases.
Examples
User: /release
Claude: Analyzes 12 commits since v0.4.1...
"I see 3 new features and 1 bug fix. I'd recommend Minor (0.5.0)."
[AskUserQuestion with Major/Minor/Patch options]
User: picks Minor
Claude: Writes release notes, shows draft
[AskUserQuestion: Notes look good?]
User: "Looks good"
Claude: Commits notes + VERSION bump, creates .release-pending.yml
[AskUserQuestion: Ship v0.5.0?]
User: "Ship it"
Claude: Tags v0.5.0, pushes, creates GitHub Release
"Released! https://github.com/OpenScribbler/syllago/releases/tag/v0.5.0"
When not to use it
- →When the user wants to manually tag a version without the full release workflow
- →When the user wants to publish to a platform other than GitHub Releases
Limitations
- →The skill is specific to the `syllago` project
- →Requires human approval at every decision point
- →The safety hook blocks `git tag` and `git push` unless `.release-pending.yml` exists
How it compares
This skill provides an interactive, guided release process with automated version bumping, release note generation, and GitHub integration, ensuring adherence to Semver and preventing errors, unlike a manual release procedure.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 3mo | No flags | Intermediate |
| release-version | 0 | 6mo | Review | Intermediate |
| chroma-release | 0 | 7mo | Review | Intermediate |
| release-buoy | 0 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
chroma-release
onevcat
Chroma 的发布一体化流程（SemVer 决策、生成 changelog、同步 CLI 版本、打 git tag、发布 GitHub Release）。当被要求进行新版本发布、更新 CHANGELOG.md、升级 `ca` CLI 版本号、创建 tag 或发布 GitHub Release 时使用。
release-buoy
WLKRLABS
Prepare and ship a new Buoy release after repo changes by updating VERSION and CHANGELOG, running the repo validation/build/package flow, installing the new local copy, tagging the release, pushing it, and verifying the GitHub release workflow.
release-rapture-mac
NoiseMeldOrg
Cut a notarized Rapture for Mac release end-to-end — run the build/sign/notarize/staple/DMG pipeline, then publish it (CHANGELOG cut, git tag at the build commit, GitHub Release with the DMG attached), and optionally install it locally. Use this whenever the user says "cut a release", "cut the relea
start
diegosouzapw
Execute a task autonomously with real-time Telegram progress updates, automatic deployment, commit, and push. No user interaction required - makes all decisions independently.
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management