agentmods.dev

tidal-sdk-ios: Command for Claude Code

.claude/commands/create-release-pr.md

create-release-pr is a command for Claude Code from tidal-music/tidal-sdk-ios. It costs 0 tokens per session (544 once invoked), scanned A, original, Apache-2.0.

A command that prepares a pull request for a new SDK release. An SDK is a package that helps developers use a software service from their code.

In plain words
What is it for?
Use it to update the SDK version, summarize changes since the previous release and open the release pull request.
Why use it?
It removes repetitive release work such as updating the version, reviewing merged changes and preparing the changelog.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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

not rated 41repo yesterday A scan 0 tokens original Apache-2.0
View source ↗ tidal-music/tidal-sdk-ios
Reuse

Borrowing it

Nothing to install: this file belongs to tidal-music/tidal-sdk-ios. 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/tidal-music/tidal-sdk-ios/main/.claude/commands/create-release-pr.md
Clone the repo
git clone --depth 1 https://github.com/tidal-music/tidal-sdk-ios

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 create-release-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/tidal-music/tidal-sdk-ios/create-release-pr/github.svg)](https://agentmods.dev/commands/tidal-music/tidal-sdk-ios/create-release-pr)
Your own site
<a href="https://agentmods.dev/commands/tidal-music/tidal-sdk-ios/create-release-pr"><img src="https://agentmods.dev/badge/commands/tidal-music/tidal-sdk-ios/create-release-pr/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 create-release-pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/tidal-music/tidal-sdk-ios/create-release-pr"><img src="https://agentmods.dev/badge/commands/tidal-music/tidal-sdk-ios/create-release-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 544 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.00000 $0.00544
Opus 5.5 $0.00000 $0.00218
Sonnet 5.5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00054

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

Security

Grade A, and why

create-release-pr 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/create-release-pr.md · 41 lines

What it actually says

Create a new SDK release PR. Execute ALL steps without asking ANY questions. Never confirm, never prompt, never wait for input.

If the user provided a version number (e.g. /create-release-pr 0.12.0), use that exact version. Otherwise, bump patch by default (e.g. 0.11.15 → 0.11.16).

Steps:

  1. Run git checkout main && git pull --ff-only origin main. If not on main, switch to it.

  2. Read current version from version.txt.

  3. Determine the new version:

    • If the user provided a specific version as argument, use it. Write it directly to version.txt.
    • Otherwise, determine bump type from the difference (patch/minor/major) or default to patch.

  4. Get one entry per merged PR since the last tag: git log <current_version>..HEAD --oneline --first-parent

  5. Read CHANGELOG.md.

  6. Generate changelog entries:

    • One entry per PR — never list individual commits within a PR.
    • Concise human-readable descriptions, not raw commit messages.
    • Format: - Description (ModuleName) — extract module from Module: Description prefix.
    • Categorize: ### Added (new features/APIs), ### Fixed (bug fixes), ### Changed (everything else).
    • Skip "Bump version", "Merge", "Update changelog" commits.
    • For "Automatic Tidal API module update" PRs: one entry - Generated API code (TidalAPI).
    • Merge with any existing [Unreleased] entries without duplicates.

  7. Write entries into [Unreleased] section of CHANGELOG.md.

  8. Run bin/bump-version.sh patch (or minor/major as needed to reach the target version). This moves [Unreleased] into the new version and updates version.txt. If the user specified an exact version, write it to version.txt after the bump script runs if the script didn't produce the right number.

  9. Verify version.txt contains the correct new version.

  10. Create branch release/<version>, commit as Bump version to <version>, push.

  11. Create draft PR: gh pr create --draft --base main --assignee @me --title "Release <version>" --body-file <tmpfile> where the body is the new changelog section.

  12. Print the PR URL.

NEVER ask questions. NEVER wait for confirmation. Just do it.

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 · 41 lines · 0 tokens per session scan A 9c15fc254386

Subscribe to this mod's changes

create-release-pr is a command published in the GitHub repository tidal-music/tidal-sdk-ios (41 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 544 tokens. 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 workflowReleases
Related

create-release-pr compared with commands from other repositories

create-release-pr next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-release-prtidal-music/tidal-sdk-iosCommand41yesterdayApache-2.0A0Claude Code
landgmickel/flow-nextCommand717yesterdayMITA13Claude Code
qualityDesko77/claude-code-skills-1cCommand90yesterdayMITA18Claude Code
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
release-managerruvnet/agentic-flowCommand838yesterdaynoneA0Claude Code
create-prdsswift/ionCommand5yesterdayMITA28Claude Code
rally-merge-prddgonzal3/rallyCommand63d agoMITA0Claude Code