agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/receiving-code-review/SKILL.md

receiving-code-review

Skill0 starsChanged 8 months agoMITView on GitHub

用于判断 review 建议该不该改：当收到 reviewer 反馈，需要先评估建议是否技术上正确、是否值得实现、是否存在误判时使用。Prefer `github-pr-review` when the main task is 操作 live GitHub PR review threads；Do not use for 直接拉取/回复 PR 线程或创建/合并 PR。

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 8 more.

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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • OpenAISkill

    dispatching-parallel-agents

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    Also in 154 projects that use this

  • OpenAISkill

    finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    Also in 144 projects that use this

  • +3 more from Leodorareluctant259
  • +2 more from openai

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 179 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 as a substitute for actually responding inside GitHub.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 179 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

receiving-code-review

Intent

  • 用于判断 review 建议该不该改：当收到 reviewer 反馈，需要先评估建议是否技术上正确、是否值得实现、是否存在误判时使用。Prefer github-pr-review when the main task is 操作 live GitHub PR review threads；Do not use for 直接拉取/回复 PR 线程或创建/合并 PR。

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: release-quality
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use as a substitute for actually responding inside GitHub.

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