ai-dial-core: Command for Claude Code

.claude/commands/release-patch.md

release-patch is a command for Claude Code from epam/ai-dial-core. It costs 16 tokens per session (1,076 once invoked), scanned A, original, Apache-2.0.

A command procedure for backporting selected merged pull requests to a release branch. Backporting means applying an existing change to an older or separate release line, then opening a pull request for it.

In plain words
What is it for?
It checks the working tree and branch, finds the commits for given pull requests, applies them to the release branch, and opens a patch pull request.
Why use it?
It reduces mistakes when selecting commits, preserving their merge order, and preparing a release patch.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

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

Reuse

Borrowing it

Nothing to install: this file belongs to epam/ai-dial-core. 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/epam/ai-dial-core/development/.claude/commands/release-patch.md
Clone the repo
git clone --depth 1 https://github.com/epam/ai-dial-core

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-patch

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/epam/ai-dial-core/release-patch"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/release-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 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,076 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.00016 $0.01076
Opus 5.5 $0.00006 $0.00430
Sonnet 5.5 $0.00003 $0.00215
Haiku 4.5 $0.00002 $0.00108

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

Security

Grade A, and why

release-patch 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 21d 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/release-patch.md · 87 lines

How it starts

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

Create a release patch

Arguments: $ARGUMENTS — first the release branch (e.g. release-0.9), then one or more merged PR numbers (e.g. 2060 2067).

development uses squash merges (<title> (#N)), so one PR is exactly one commit.

Preconditions

  • Abort if fewer than 2 arguments are given.
  • Abort if the working tree is dirty (git status --porcelain --untracked-files=no is not empty); untracked files are ignored.
  • git fetch origin --tags, then verify origin/{release} exists. If not, list available origin/release-* branches and stop.

Steps

  1. Check out and update the release branch:

    git checkout {release}
    git pull origin {release}
    
  2. Resolve commits for all PRs up front. For each PR number {n}:

    • gh pr view {n} --json state,mergeCommit — use mergeCommit.oid when state is MERGED.
    • If that fails, fall back to git log origin/development --format=%H --grep='(#{n})'.
    • If the PR is not merged or no commit is found, stop and report.

    Sort the commits by merge order on origin/development (oldest first, e.g. git rev-list --reverse origin/development filtered to the resolved SHAs), regardless of argument order. Print the final PR → SHA order before continuing.

  3. Create the patch branch. Compute {next_release_version}: take git describe --tags --abbrev=0 origin/{release} (e.g. 0.9.2) and increment the patch number (0.9.3). If no tag is found, ask the human. A previous aborted run or an open patch PR leaves the tag unchanged, so first check that the name is free locally (git rev-parse --verify --quiet patch-{next_release_version}) and on origin (git ls-remote --exit-code --heads origin patch-{next_release_version}). If either exists, ask the human whether to delete it or use a suffix (patch-{next_release_version}-2); never overwrite it. Then:

    git checkout -b patch-{next_release_version}
    

    Never push to the release branch directly.

  4. Cherry-pick each commit in order:

    git cherry-pick -x {sha}
    

    -x appends a (cherry picked from commit ...) trailer; keep the original message.

Read the full file on GitHub · 87 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. 21d ago First seen · 87 lines · 16 tokens per session scan A ae4a7643e1ab

Subscribe to this mod's changes

release-patch is a command published in the GitHub repository epam/ai-dial-core (661 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,076 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-10-07.

Related

Other commands, from other repositories