A guided release workflow for the Syllago project. It reviews changes, suggests a semantic version number, prepares release notes, and publishes a GitHub release with approval at each decision.

Use it when creating a release, tagging a version, changing the VERSION file, or publishing to GitHub Releases.

It reduces the manual work and uncertainty involved in deciding what version to publish and preparing a release.

How OpenScribbler/syllago configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to OpenScribbler/syllago. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/OpenScribbler/syllago/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/OpenScribbler/syllago

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openscribbler/syllago/release/github.svg)](https://agentmods.dev/skills/openscribbler/syllago/release)

Your own site

<a href="https://agentmods.dev/skills/openscribbler/syllago/release"><img src="https://agentmods.dev/badge/skills/openscribbler/syllago/release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openscribbler/syllago/release"><img src="https://agentmods.dev/badge/skills/openscribbler/syllago/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 740 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.00740
Opus 5.5	$0.00013	$0.00296
Sonnet 5.5	$0.00006	$0.00148
Haiku 4.5	$0.00003	$0.00074

Measured 1mo ago against content hash 18eec2b0ed35, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/release/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.yaml schema 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

Read the full file on GitHub · 84 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 84 lines · 32 tokens per session scan A 18eec2b0ed35

Subscribe to this mod's changes

release is a skill published in the GitHub repository OpenScribbler/syllago (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 740 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases ai-agents ai-tools cli developer-tools devex go

git-flow-pr

Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…

soulcodex/agentic · 103 tokens

write-changelog

Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.

soulcodex/agentic · 73 tokens

syllago: Skill for Claude Code