agentmods.dev

Monomi: Command for Claude Code

.claude/commands/run-release.md

run-release is a command for Claude Code from sumihiro3/Monomi. It costs 57 tokens per session (1,674 once invoked), scanned A, original, MIT.

A release command that runs a configured software delivery workflow. It reads and checks the project's workflow configuration before starting.

In plain words
What is it for?
Use it to run a named release or the current branch through the project's automated release pipeline, with an option to pause before committing.
Why use it?
It keeps implementation, checks, review, documentation updates, commits, and pull-request creation in one controlled process, and stops when required configuration is missing or invalid.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is sumihiro3/Monomi's own configuration. It tells Claude Code how to work on Monomi 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 Monomi configures →

not rated 2repo 3mo ago A scan 57 tokens original MIT
View source ↗ sumihiro3/Monomi npmjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to sumihiro3/Monomi. 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/sumihiro3/Monomi/main/.claude/commands/run-release.md
Clone the repo
git clone --depth 1 https://github.com/sumihiro3/Monomi

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 run-release

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

agentmods 80×15 button for run-release

Your own site · 80×15
<a href="https://agentmods.dev/commands/sumihiro3/monomi/run-release"><img src="https://agentmods.dev/badge/commands/sumihiro3/monomi/run-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,674 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.00057 $0.01674
Opus 5.5 $0.00023 $0.00670
Sonnet 5.5 $0.00011 $0.00335
Haiku 4.5 $0.00006 $0.00167

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

Security

Grade A, and why

run-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 2mo 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/commands/run-release.md · 49 lines

How it starts

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

/run-release — リリース自動パイプラインの起動

確定済み要件(config の requirementsPath が指す requirements.md)を入力に、実装→検査ループ→レビューループ→known-issues 起票→doc 同期→論理単位コミット→PR 作成までを統括する run-release ワークフローを起動する。

引数: $ARGUMENTS(対象リリース識別子。例: release-1-login-form。省略時は現在のブランチ名をリリース識別子とみなす。autoApprove=false を付けると config の値に関わらずコミット直前で停止する)

進め方

  1. config の読込: .claude/workflow.config.json を Read する。ファイルが無い・読めない場合は「.claude/workflow.config.json がありません」と明示し、起動しない。値を推測で補完して起動することを禁止する。.claude/config.schema.json を参照して config を作成するよう案内して終了する

  2. スキーマ整合の確認: .claude/config.schema.json を Read し、手順1で読み込んだ config が構造的に整合するかを確認する:

    • スキーマの required に列挙されたトップレベルキーがすべて存在する
    • configVersion が 1(エンジン要求版)である
    • checks・reviewDimensions が非空配列で、各要素が必須フィールド(key/cmd/cwd、key/prompt)を持つ
    • automation に各上限値と severityGate が揃っている
    • 違反があれば違反箇所を列挙して起動しない(スキーマ検証ツールが利用可能な環境ならそれで検証してよい。無ければ上記の構造照合で足りる)

  3. リリース識別子の決定: $ARGUMENTS で指定があればそれを、無ければ現在のブランチ名(git branch --show-current)をリリース識別子とする。現在ブランチが config の baseBranch と同一の場合は run-release の Gate 0 で拒否されるため起動せず、リリースブランチへの切替(または /refine-requirements からのやり直し)を案内する

  4. 起動: 以下で起動する。config には手順1で読み込んだファイル内容をそのまま渡す(要約・省略・補完をしない):

    Workflow({scriptPath: ".claude/workflows/run-release.js", args: {release: "<リリース識別子>", config: <手順1で読み込んだ config>, autoApprove: <config.automation.autoApprove>}})
    • 起動は常に scriptPath 指定とする。name 指定({name: "run-release"})は、新規追加されたワークフローが同一セッション内で name 解決されない既知の罠があるため使わない
    • $ARGUMENTS に autoApprove=false の指定があれば、args.autoApprove をそれで上書きする(既定は config.automation.autoApprove)

  5. 戻り値の読み取りと報告: 後述の「戻り値の読み方」に従って結果を要約し、ユーザーに報告する

戻り値の読み方(完了・停止時)

run-release は完了時・停止時のいずれも戻り値で結果を返す(いずれの場合も push 通知が送信される)。以下の順で読み取って報告する:

  1. 終了区分の特定: まず次のどれで終わったかを特定する
    • 通常 PR 作成: 全ゲート通過。PR の URL と PR 本文の要点(FR/AC 充足状況・最終検査結果・起票 ID・消費サマリー)を報告して完了
    • draft PR 降格: high 所見の残存・手動検証必須 AC の未実施・最終検査の収束不能のいずれか。未解決事項は PR 本文に明記されているので、残存項目とその解消手順を要約して報告する
    • PR なしで停止: Gate 0 preflight 拒否(ダーティツリー / ブランチ不一致 / 要件が「ステータス: 確定」でない / configVersion 不一致)、critical 所見の残存、収束不能、エージェント起動数上限超過のいずれか。停止理由を報告し、ブランチ・作業状態は保全されている(reset されていない)ことを添える
    • コミット直前停止(autoApprove=false 起動時の正常経路): 戻り値に含まれるコミット案・PR 案を提示し、/logical-commits(対話承認)へ引き継ぐ
  2. 起票結果: 未対応所見・収束不能分は known-issues に起票される。新規起票された ID・既存項目へ追記された ID を報告する。解決済みログへの移動提案(提案 diff)が含まれる場合は、適用可否をユーザーに確認する
  3. 消費サマリー: フェーズ別のエージェント起動数を報告に含める(上限到達で停止した場合の一次情報になる)

Read the full file on GitHub · 49 lines

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 · 57 tokens per session scan A d4ffb1c92617

Subscribe to this mod's changes

run-release is a command published in the GitHub repository sumihiro3/Monomi (2 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,674 once invoked, about $0.0002 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.

CI and CDClaude CodeDevOps and cloudGit and workflowReleasesclidashboardinkmonitoringnodejs
Related

Other commands, from other repositories

release-swarm

Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.

ruvnet/RuView · 0 tokens

post-release.en

Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.

fitlab-ai/agent-infra · 4 tokens

ci

Run CI validation, create PRs, and merge on green.

Generous-Corp/pulp · 14 tokens

deploy

Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.

NickRomanek/clawbridge · 0 tokens

release

Publish a release branch.

Goldziher/ai-rulez · 4 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.

dsswift/ion · 28 tokens