Community写作与编辑github.com

pr-description-writer

Writes a complete pull request description from the branch diff, including summary, changes, test plan, and risk notes. Use when the user asks to write a PR description, open a pull request, summarize a branch, draft a merge request, or explain what a branch changes. Do not use for reviewing code quality or writing commit messages.

pr-description-writer 是什么?

pr-description-writer is a Claude Code agent skill that writes a complete pull request description from the branch diff, including summary, changes, test plan, and risk notes. Use when the user asks to write a PR description, open a pull request, summarize a branch, draft a merge request, or explain what a branch changes. Do not use for reviewing code quality or writing commit messages.

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/teejayfpi/agensi-skills/tree/HEAD/repo-maintenance-pack/skills/pr-description-writer

Installed? Explore more 写作与编辑 skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

PR Description Writer

Write the description a reviewer wishes they had. Every claim must trace to the diff.

Procedure

  1. Determine the base branch. Use the one the user names. Otherwise try git merge-base HEAD main then master. State which base you used.
  2. Collect the change set:
    • git diff <base>...HEAD --stat for the file summary.
    • git diff <base>...HEAD for the substance.
    • git log <base>..HEAD --pretty=format:'%h %s' for the commit list.
  3. Identify the purpose. Read the diff, not just the commit subjects. If the purpose is not evident, write what the change does and mark the intent as "unclear" rather than inventing a motivation.
  4. Find the test evidence. Look for changed or added test files, and for commands in CI config, Makefile, package.json scripts, or the README. Report only tests that exist in the repo.
  5. Note risk. Flag changes to public interfaces, config keys, database schema, authentication, or anything without test coverage.

Output template

Use this structure. Drop a section only when it would be empty; never leave placeholder text.

## Summary

One or two sentences: what this changes and why.

## Changes

- `path/to/file`: what changed and why
- `path/to/other`: what changed and why

## How to test

1. Step a reviewer can run
2. Expected result

## Risk and rollback

- Risk: what could break, or "Low, isolated to <area>"
- Rollback: how to revert safely

## Notes for reviewers

Anything that needs context: a tricky trade-off, a follow-up, a part that is intentionally out of scope.

Rules

  • Group the change list by intent (feature, refactor, tests, docs), not by file order, when the diff is larger than about ten files.
  • Never write "This PR does X" without a line in the diff that shows X.
  • Keep the summary under four lines. Reviewers read it first and often only it.
  • Do not invent test steps. If there are no tests, write "No automated tests; manual check: ".
  • Do not add an AI-authorship footer unless the user asks.

Supporting file

references/pr-template.md holds a longer annotated template for large or multi-part changes. Read it when the diff touches more than about fifteen files.

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

相关技能