skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Coding / Requesting Code Review Skill by @obra
The skill is the skills/requesting-code-review folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Sets out when an agent should ask for a review and how to ask well: after completing tasks, after major features and before merging, with an example and a list of rationalisations and red flags that signal a review is being skipped.
The original SKILL.md is organised into these sections:
Written and maintained by @obra. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
-----|---------| | "I'll just review the diff myself instead of dispatching a reviewer" | You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. | | "The reviewer needs my whole session history to understand the change" | Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. | ## Red Flags **Never:** - Skip review because "it's simple" - Ignore Critical issues - Proceed with unfixed Important issues - Argue with valid technical feedback **If reviewer wrong:** - Push back with technical reasoning - Show code/tests that prove it works - Request clarification See template at: [code-reviewer.md](code-reviewer.md)
Excerpt only, quoted from the author's repository. Open the repository for the complete file.