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.
curl -O https://raw.githubusercontent.com/tidal-music/tidal-sdk-ios/main/.claude/commands/create-release-pr.mdgit clone --depth 1 https://github.com/tidal-music/tidal-sdk-iosWrote 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/commands/tidal-music/tidal-sdk-ios/create-release-pr)<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="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.00000 | $0.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 8d 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.
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:
-
Run
git checkout main && git pull --ff-only origin main. If not on main, switch to it. -
Read current version from
version.txt. -
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.
- If the user provided a specific version as argument, use it. Write it directly to
-
Get one entry per merged PR since the last tag:
git log <current_version>..HEAD --oneline --first-parent -
Read
CHANGELOG.md. -
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 fromModule: Descriptionprefix. - 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.
-
Write entries into
[Unreleased]section ofCHANGELOG.md. -
Run
bin/bump-version.sh patch(orminor/majoras needed to reach the target version). This moves[Unreleased]into the new version and updatesversion.txt. If the user specified an exact version, write it toversion.txtafter the bump script runs if the script didn't produce the right number. -
Verify
version.txtcontains the correct new version. -
Create branch
release/<version>, commit asBump version to <version>, push. -
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. -
Print the PR URL.
NEVER ask questions. NEVER wait for confirmation. Just do it.
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.
- 8d ago First seen · 41 lines · 0 tokens per session scan A 9c15fc254386
create-release-pr is a command published in the GitHub repository tidal-music/tidal-sdk-ios (41 stars, last pushed 3d ago), 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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.