monorepo: Skill for Claude Code

.claude/skills/release-workflow/SKILL.md

release-workflow is a skill for Claude Code from logosdx/monorepo. It costs 25 tokens per session (442 once invoked), scanned A, original, BSD-3-Clause.

A release process for publishing changes to npm, the package registry commonly used for JavaScript and TypeScript libraries.

In plain words
What is it for?
Use it when releasing npm changes from a feature branch, including creating changesets, opening a pull request, watching CI, and publishing.
Why use it?
It organizes version notes, commits, pull requests, automated checks, merges, and publishing so a release follows the required project workflow.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is logosdx/monorepo's own configuration. It tells Claude Code how to work on monorepo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything monorepo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to logosdx/monorepo. 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/logosdx/monorepo/master/.claude/skills/release-workflow/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/logosdx/monorepo

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.

agentmods badge for release-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/logosdx/monorepo/release-workflow/github.svg)](https://agentmods.dev/skills/logosdx/monorepo/release-workflow)
Your own site
<a href="https://agentmods.dev/skills/logosdx/monorepo/release-workflow"><img src="https://agentmods.dev/badge/skills/logosdx/monorepo/release-workflow/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.

agentmods 80×15 button for release-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/logosdx/monorepo/release-workflow"><img src="https://agentmods.dev/badge/skills/logosdx/monorepo/release-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 442 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00442
Opus 5.5 $0.00010 $0.00177
Sonnet 5.5 $0.00005 $0.00088
Haiku 4.5 $0.00003 $0.00044

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

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (release.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-workflow/SKILL.md · 49 lines

What it actually says

Release Workflow

Quick Start

# From a feature branch with changes ready:
/release-workflow

Critical Rules

  1. Must be on feature branch - Not master/main. Create branch first if needed.
  2. Session reports drive changesets - Reads tmp/reports/new/ for context.
  3. Two-phase process - First: changesets + commit. Second: automated PR flow.
  4. Script handles git/github - release.mjs automates CI waits and merges.

Workflow

  1. Read session reports from tmp/reports/new/ to understand changes
  2. Invoke /changeset-writer skill to create changesets
  3. Invoke /git-committer skill to commit all changes
  4. Run pnpm zx .claude/skills/release-workflow/release.mjs to automate:
    • Push branch, create PR to master
    • Wait for CI, merge PR (squash)
    • Wait for Version Packages PR, merge it
    • The version bump on master triggers the publish workflow; wait for it

Manual Steps (if script fails)

Step Command
Push & PR git push -u origin HEAD && gh pr create --base master --fill
Watch CI gh run watch $(gh run list -b BRANCH -L1 --json databaseId -q '.[0].databaseId')
Merge PR gh pr merge --squash --delete-branch
Version PR gh pr list --search "Version Packages" then gh pr merge NUM --squash
Watch publish gh run watch $(gh run list -b master -w publish.yml -L1 --json databaseId -q '.[0].databaseId')

References

Files

What ships with it

1 file 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.

  1. 2mo ago First seen · 49 lines · 25 tokens per session scan A 4fc9e821c9b6

Subscribe to this mod's changes

release-workflow is a skill published in the GitHub repository logosdx/monorepo (7 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 25 tokens to every session and 442 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-31.

Related

release-workflow compared with skills from other repositories

release-workflow next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-workflowlogosdx/monorepoSkill78d agoBSD-3-ClauseA25Claude Code
release-announcementpaperclipai/paperclipSkill111kyesterdayMITA42Claude Code, Codex
releasethedotmack/claude-memSkill114kyesterdayApache-2.0A13Claude Code
release-notesphuryn/pm-skillsSkill28k8d agoMITA57Claude Code
multi-agent-release-managerchromium/chromiumSkill25kyesterdayBSD-3-ClauseA27Claude Code, Codex
pack-submitaeonfun/aeonSkill788yesterdayMITA27Claude Code, Codex
updater_guidesiddsachar/row-botSkill1.7kyesterdayApache-2.0A22Claude Code, Codex