receiving-code-review

Guide engineers through a six-step code review feedback process with testing.

Updated Apr 16, 2014
One-click install
npx skills add https://github.com/minhhh/dotfiles --skill receiving-code-review-minhhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/minhhh/dotfiles/tree/main/ai/.ai/gemini-superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/minhhh/dotfiles --skill receiving-code-review-minhhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often requires careful technical evaluation before acting; this guide ensures clear understanding, verification against the codebase, and cautious, itemized implementation.

Core Features & Use Cases

  • Restate requirements, ask clarifying questions, verify against codebase reality, and provide reasoned pushback when needed.
  • Implement one item at a time after verification, testing each before proceeding.
  • Use in situations where feedback is unclear or potentially technically questionable.

Quick Start

Read the full feedback, restate the requirement in your own words, verify it against the codebase, evaluate its technical correctness, respond with rationale, and implement items one by one while testing.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle code review feedback that seems technically questionable?

Handle code review feedback by restating requirements, verifying against the codebase, evaluating technical correctness, and providing reasoned pushback before implementing changes incrementally with tests.

What is the best way to verify code review comments against the actual codebase?

Verify code review comments by checking them against codebase reality, evaluating technical correctness, and asking clarifying questions when requirements are unclear or changes are high-risk.

How do I push back on code review feedback without causing conflict?

Push back on code review feedback by providing reasoned rationale after verifying the comment against the codebase and evaluating its technical correctness.

When should I use a structured process for code review feedback?

Use a structured process for code review feedback when requirements are unclear, changes are high-risk, or verification against the codebase is essential before implementation.

How do I implement code review changes incrementally?

Implement code review changes incrementally by addressing one item at a time after verification, testing each change before proceeding to the next item.