reviewing-pull-requests
Reviews a pull request diff against a structured rubric covering correctness, tests, security, and style, then produces a prioritized comment list. Use when the user asks to review a PR, audit a diff, or check changes before merging.
- License 许可
- MIT
- 最近更新
- 2026-06-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- reviewing-pull-requests
- description
- Reviews a pull request diff against a structured rubric covering correctness, tests, security, and style, then produces a prioritized comment list. Use when the user asks to review a PR, audit a diff, or check changes before merging.
02 资源文件 3
- 参考文档references/reference.md2.3 KB
- 参考文档test-prompts.md1.3 KB
- 参考文档tests.md3.0 KB
03 SKILL.md 正文
Reviewing Pull Requests
When to use
The user explicitly asks to review, audit, or critique a pull request, a diff, or staged changes — including phrasing like "review this PR", "look over my diff", "anything risky in these changes".
Steps
- Fetch the diff with whatever tool fits the context (
git diff,gh pr diff, file contents the user pasted). - Apply the rubric in reference.md section by section.
- For each finding, classify priority: blocker, important, or
nit. Include
file:linereferences. - Emit the report in the output format below. Lead with blockers; nits go last and may be omitted if the diff is small.
Output
## Blockers
- file:line — issue + suggested fix
## Important
- file:line — issue + suggested fix
## Nits (optional)
- file:line — minor issue
## Summary
<one sentence: ship / hold / needs-rework>
Notes
- Don't restate what the diff already shows. A reviewer's job is to flag what's wrong or missing, not narrate the change.
- If you can't tell whether something is correct without more context (the caller, the schema, the test that exercises it), say so — don't guess.
04 同仓库更多 Skills
writing-release-notes
Generates release notes from merged pull requests, grouping the changes into features, fixes, and chores so the notes read clearly. Use when the user asks to draft release notes, write a changelog, summarize merged PRs into release notes, or any time you need to write something describing recent code changes.
generating-ai-ideas
Orchestrates a council of specialized perspectives to generate, stress-test, and refine high-quality, sellable AI-related business and product ideas. Use when the user wants validated AI business opportunities, AI product concepts, or AI tooling ideas with clear go-to-market paths.
winpath-in-reference
Audits widget docs for path portability. Use when the user asks to audit fixture path portability, scan widget references for backslash paths, or vet doc hygiene.
vague-trigger
Generates widget summaries for engineers and is helpful for data processing tasks generally.
stale-tests
Refreshes widget fixture baselines on demand. Use when the user asks to refresh fixture baselines, re-verify widget scenarios, or rebaseline gizmo outputs.
smell-in-script
Installs the widget toolchain via the bundled script. Use when the user asks to install the widget toolchain, bootstrap gizmo tooling, or set up fixture dependencies.