pr-authoring

仓库创建 2026年7月26日最近提交 19 小时前SkillHot 收录 15 小时前

这个 Skill 做什么

教你写让人秒懂的 PR 标题和描述：清楚说明改了什么、为什么改、如何验证，内容要与改动规模匹配。在准备提交 pull request 时使用，写给不了解背景的审查者看。好处是能显著缩短 review 时间，让小改动快速合入，大改动也能被高效审查。

▸ 展开 SKILL.md 英文原文

How to write a pull request - a title and a description that tell the reviewer what changed, why, and how to verify it, scaled to the size of the change. Use when composing a PR for delivery.

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/pr-authoring/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/pr-authoring/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# PR Authoring

A pull request exists to **communicate with the reviewer**, and the author controls review latency: a clear "what + why + how to verify" gets merged in minutes; a bare diff with "various fixes" sinks to the bottom of the queue. Write the description for someone walking in blind - not from your own memory of the work.

## Title

`type(scope): subject` - imperative, ≤50 chars, no period (`feat(auth): add Google OAuth2 sign-in`). It becomes the squash commit on the default branch, so it's permanent history, not a label. Reference the issue: end with `(closes #<n>)` or put `Closes #<n>` in the body. If you can't title the change in one line, it's too big - it should be more, smal

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有