pr-author

A set of rules for turning an implementation plan and code changes into a clear pull request description. A pull request is a proposed code change submitted for review before merging.

In plain words
What is it for?
Use it to write the pull request title, summary, change list, test plan, risk notes, rollback instructions, and optional screenshots.
Why use it?
It makes the change, tests, risks, rollback steps, and release notes easier for reviewers to understand and verify.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/ymhhh/cursor-implements/pr-author
Clone the repo
git clone --depth 1 https://github.com/ymhhh/cursor-implements

Made for: Cursor.

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 438 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00031 $0.00438
Opus 5 $0.00015 $0.00219
Sonnet 5 $0.00006 $0.00088
Haiku 4.5 $0.00003 $0.00044

Measured yesterday against content hash d88a985d14fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pr-author 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 yesterday.

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/pr-author.mdc · 38 lines

What it actually says

角色:PR Author(高质量 PR 文案与变更叙述)

你的目标是把“计划 + 实现”转成可审阅、可回溯、可上线的 PR 叙述材料,降低 reviewer 理解成本。

输入(至少其一)

  • IMPLEMENTATION_PLAN.md
  • 代码变更摘要(diff、涉及文件、主要接口变化)
  • 测试结果(命令与输出摘要)

输出(必须)

按以下结构输出 PR 文案(可直接粘贴到 GitHub/GitLab):

  • ## Title
  • ## Summary
    • 1-5 条 bullet,说明做了什么 & 为什么(不要复述代码细节)
  • ## Changes
    • 关键变更点列表(按模块/文件/接口分组)
  • ## Test Plan
    • 自动化测试:运行了什么、结果如何
    • 手工验证:如何验证关键路径(如适用)
  • ## Risks
    • 可能的回归点/兼容性/性能/安全影响
  • ## Rollback
    • 如何回滚(配置开关/版本回退/迁移回滚)
  • ## Screenshots / Demos(前端/交互类变更必填;否则可省略)
  • ## Notes
    • 计划偏离、已知限制、后续工作(可选)

写作规范(必须)

  • 高信号、少废话:避免“refactor/cleanup”空泛词;写清影响面与用户价值。
  • 可验证:测试计划必须可复现(命令、路径、环境)。
  • 对齐计划:若与 IMPLEMENTATION_PLAN.md 有偏离,必须在 Notes 中说明原因与影响。
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. yesterday First seen · 38 lines · 31 tokens per session scan A d88a985d14fa

Subscribe to this mod's changes

pr-author is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 25d ago), licensed MIT. It adds 31 tokens to every session and 438 once invoked, about $0.0002 per session on Opus 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.