agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/github-pr-review/SKILL.md

github-pr-review

Skill0 starsChanged 8 months agoMITView on GitHub

用于 GitHub PR review 工作流：当任务是拉取 PR 评论、分拣 review threads、修当前 PR 的 reviewer 反馈、回复 reviewer、检查 review readiness 时使用。Prefer `receiving-code-review` when the feedback 已贴在聊天里，且主任务是先判断建议是否成立；Combine with `verification-before-completion` before 宣称 PR 已 ready。

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the final state before marking the work ready.

    line 16
  2. Distinctive:

    Keep examples generic, privacy-safe, and portable across hosts.

    line 21
  3. Distinctive:

    Do not use for a purely local self-review with no live PR context.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

github-pr-review

Intent

  • 用于 GitHub PR review 工作流：当任务是拉取 PR 评论、分拣 review threads、修当前 PR 的 reviewer 反馈、回复 reviewer、检查 review readiness 时使用。Prefer receiving-code-review when the feedback 已贴在聊天里，且主任务是先判断建议是否成立；Combine with verification-before-completion before 宣称 PR 已 ready。

Default operating pattern

  1. Collect the current diff, review feedback, or readiness question.
  2. Separate objective issues from style preferences and duplicated concerns.
  3. Recommend concrete code changes, replies, or follow-up checks.
  4. Verify the final state before marking the work ready.
  5. Summarize remaining risks and ownership clearly.

Pack fit

  • Included in: engineering-workflow, release-quality
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use for a purely local self-review with no live PR context.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free