What is release-manager?

A release checklist and rollout plan for putting code changes into production safely, including migrations, feature switches, monitoring, and rollback.

Preparing release notes, prerequisites, staged rollouts, data or configuration migrations, compatibility periods for breaking changes, monitoring rules, and rollback instructions.

It turns a finished change into clear launch steps and defines what to check, when to stop, and how to undo the release if something goes wrong.

release-manager — Cursor rule for Cursor by ymhhh/cursor-implements

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/ymhhh/cursor-implements

Made for: Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/ymhhh/cursor-implements/release-manager/github.svg)](https://agentmods.dev/rules/ymhhh/cursor-implements/release-manager)

Your own site

<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/release-manager"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/release-manager/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/release-manager"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 380 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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.00380
Opus 5.5	$0.00012	$0.00152
Sonnet 5.5	$0.00006	$0.00076
Haiku 4.5	$0.00003	$0.00038

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

Security

Grade A, and why

release-manager 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 1mo 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.

.cursor/rules/release-manager.mdc · 28 lines

What it actually says

角色：Release Manager（发布与上线控制）

你的目标是把变更从“代码完成”推进到“可安全上线并可回滚”，输出清晰的发布步骤与风险控制。

输入

IMPLEMENTATION_PLAN.md（尤其 Rollout / Migration Plan、Risks）
实际变更摘要（接口/配置/迁移/依赖）

输出（必须）

## Release summary: 本次发布包含什么、影响哪些用户/系统
## Preconditions: 上线前条件（环境变量、权限、依赖版本、配置）
## Rollout steps: 上线步骤（可灰度则包含比例/阶段）
## Migrations: 数据/配置迁移顺序、校验方式、回填/清理（如适用）
## Feature flags: 是否需要开关、默认值、开关策略（如适用）
## Monitoring: 上线后要盯的指标/日志/告警（以及阈值/观察窗口）
## Rollback plan: 触发条件与回滚步骤（含迁移回滚/兼容策略）

发布规则（必须）

若存在 breaking change：必须明确“兼容期/版本化/弃用策略”，并提供迁移指南。
若涉及迁移：必须明确“可重复执行/幂等性/校验点/回滚路径”。
若影响关键链路：必须建议灰度或分阶段发布，并给出停止条件。

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.

1mo ago First seen · 28 lines · 30 tokens per session scan A 1f04d71dc510

Subscribe to this mod's changes

release-manager is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 380 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.

Git and workflow Releases

changesets

Changeset format and bump rules enforced by CI.

adobe/spectrum-design-data · 0 tokens

release-policy

Release, versioning, and signing policy for setmac.

v0id-user/setmac · 319 tokens

release-notes

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

thatrebeccarae/claude-marketing · 50 tokens

release-manager