agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/receiving-code-review/SKILL.md

receiving-code-review

Skill1 starsChanged 5 months agoMITView on GitHub

Turn review feedback into a prioritized response plan, fix real issues, and preserve explicit decisions for deferred items. Use when a human or agent reviewer provides comments, blockers, test failures, or merge-readiness feedback. Review comments, current diff, spec/plan, validation output, project constraints, and user priorities. If the review request asks for an intelligence map, or if the change is complex enough to warrant one, run vibe-review-intelligence or follow skills/core/code-intelligence-review/SKILL.md before analysing feedback. The intelligence map provides a structural baseline —…

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 6 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

    using-superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    Also in 112 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 2

    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:

    Use when a human or agent reviewer provides comments, blockers, test failures, or merge-readiness feedback.

    line 21
  2. Distinctive:

    If feedback conflicts with requirements, ask or explain the trade-off before editing.

    line 35

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

Skill: Receiving Code Review

Purpose

Turn review feedback into a prioritized response plan, fix real issues, and preserve explicit decisions for deferred items.

When to use

Use when a human or agent reviewer provides comments, blockers, test failures, or merge-readiness feedback.

Inputs

Review comments, current diff, spec/plan, validation output, project constraints, and user priorities.

Optional: use an intelligence map

If the review request asks for an intelligence map, or if the change is complex enough to warrant one, run vibe-review-intelligence or follow skills/core/code-intelligence-review/SKILL.md before analysing feedback. The intelligence map provides a structural baseline — call graph, dependency chains, data flow, and test gaps — that helps you classify feedback by true impact. A blocker that affects a widely-called function is more urgent than one in a leaf module; the map reveals this quickly.

Workflow

  1. Classify feedback as blocker, correctness issue, maintainability suggestion, question, or optional follow-up.
  2. Address blockers and correctness issues before style preferences.
  3. If feedback conflicts with requirements, ask or explain the trade-off before editing.
  4. Make focused fixes and avoid using review as permission for broad rewrites.
  5. Re-run relevant checks after changes.
  6. Respond with what changed, what was verified, and what remains deferred with rationale.

Outputs

A review-response summary, focused follow-up patch, updated validation status, and any deferred items with rationale.

Failure modes

  • Treating every suggestion as mandatory scope expansion.
  • Dismissing blockers without evidence.
  • Fixing review comments but not rerunning relevant checks.
  • Leaving deferred decisions undocumented.

Verification checklist

  • Feedback is triaged by severity.
  • Blockers are resolved or escalated.
  • Checks were rerun where relevant.
  • Deferred items have rationale and owner/next step.

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