Borrowing it
Nothing to install: this file belongs to basher83/lunar-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/basher83/lunar-claude/main/.claude/skills/release-workflow/SKILL.mdgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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.
[](https://agentmods.dev/skills/basher83/lunar-claude/release-workflow)<a href="https://agentmods.dev/skills/basher83/lunar-claude/release-workflow"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/release-workflow.svg" alt="Measured on agentmods" height="20"></a>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.00033 | $0.00901 |
| Opus 5 | $0.00016 | $0.00451 |
| Sonnet 5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
release-workflow 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Project-specific release conventions for lunar-claude. For the interactive
release workflow, use the /generate-changelog command from the git-workflow
plugin.
Current Release State
- Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet" - Marketplace version: !
jq -r '.metadata.version' .claude-plugin/marketplace.json - Unreleased commits: !
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null)..HEAD 2>/dev/null | wc -l | tr -d ' '
Version Scheme
- Semantic versioning:
MAJOR.MINOR.PATCH - Tag format:
v0.x.y(prefixed withv) - Marketplace and plugin manifests track versions independently
Version Bump Decision
| Commit types present | Bump level |
|---|---|
BREAKING CHANGE: in footer or ! after type |
Major |
feat: (new features) |
Minor |
fix:, docs:, refactor:, perf:, test:, chore: only |
Patch |
Commit → Changelog Group Mapping
git-cliff (cliff.toml) maps conventional commits to changelog groups:
| Commit prefix | Changelog group |
|---|---|
feat |
🚀 Features |
fix |
🐛 Bug Fixes |
refactor |
🚜 Refactor |
doc |
📚 Documentation |
perf |
⚡ Performance |
style |
🎨 Styling |
test |
🧪 Testing |
chore, ci |
⚙️ Miscellaneous Tasks |
| body contains "security" | 🛡️ Security |
revert |
◀️ Revert |
Auto-Skipped Commits
These are filtered out of the changelog automatically:
chore(release): prepare for— release prep commitschore(deps*)— dependency updates (Renovate/Dependabot)chore(pr)/chore(pull)— PR merge housekeeping
Files to Update on Release
- CHANGELOG.md — Generated by
git-cliff --tag vX.Y.Z -o CHANGELOG.md .claude-plugin/marketplace.json— Updatemetadata.version- Plugin manifests — Update
versionin each changed plugin'splugins/<cat>/<name>/.claude-plugin/plugin.json(only if that plugin changed)
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.
- 7d ago First seen · 94 lines · 33 tokens per session scan A e8bb3e40a874
release-workflow is a skill published in the GitHub repository basher83/lunar-claude (22 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 901 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.