requesting-code-review
starsforks
How to install requesting-code-review?
heymegabyte/claude-skills/requesting-code-review
$npx -y skills add heymegabyte/claude-skills --skill requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
SKILL.md
| 1 | # Requesting Code Review |
| 2 | |
| 3 | Dispatch a reviewer subagent on completed work. Feed it crafted context (description + requirements + git range) — never your session history. Keeps the reviewer on the work product and preserves your own context. |
| 4 | |
| 5 | **Review early, review often.** |
| 6 | |
| 7 | Brian's stack already ships a purpose-built `code-reviewer` agent + the **Agent Diversity Review gate** (`[[agent-selection]]`). Prefer the named agent over a bare `general-purpose` spawn; this skill is the request protocol that complements both. |
| 8 | |
| 9 | ## When to request |
| 10 | |
| 11 | Mandatory: |
| 12 | |
| 13 | 1. Before merge to main |
| 14 | 2. After each task in subagent-driven development |
| 15 | 3. After completing a major feature |
| 16 | |
| 17 | Optional: when stuck (fresh eyes), before a refactor (baseline), after a complex bugfix. |
| 18 | |
| 19 | ## How to request |
| 20 | |
| 21 | 1. Get SHAs — `BASE_SHA=$(git rev-parse origin/main)`, `HEAD_SHA=$(git rev-parse HEAD)`. |
| 22 | 2. Spawn the `code-reviewer` agent (or `general-purpose` filling [code-reviewer.md](code-reviewer.md)). |
| 23 | 3. Fill placeholders: `{DESCRIPTION}` (what you built), `{PLAN_OR_REQUIREMENTS}` (what it should do), `{BASE_SHA}`, `{HEAD_SHA}`. |
| 24 | |
| 25 | ## Act on feedback |
| 26 | |
| 27 | 1. Fix Critical immediately; fix Important before proceeding. |
| 28 | 2. Note Minor for later. |
| 29 | 3. Push back with technical reasoning if the reviewer is wrong — see `[[receiving-code-review]]`. |
| 30 | |
| 31 | ## Never |
| 32 | |
| 33 | - Skip review because "it's simple". |
| 34 | - Ignore Critical, or proceed with unfixed Important. |
| 35 | - Argue with valid technical feedback. |
| 36 | |
| 37 | <!-- budget: ~40 --> |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
