receiving-code-review

Evaluate code-review feedback with a structured six-step response workflow.

6|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/futuregerald/futuregerald-claude-plugin --skill receiving-code-review-futuregerald
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/futuregerald/futuregerald-claude-plugin/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/futuregerald/futuregerald-claude-plugin --skill receiving-code-review-futuregerald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a disciplined approach to handling code-review feedback: evaluating requirements, verifying against the codebase, and pushing back with technical reasoning.

Core Features & Use Cases

  • Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to ensure changes are correct and justified.
  • Clarity when unclear: halt and ask clarifying questions before acting when any item is ambiguous.
  • Source-specific handling: distinguish trusted partner feedback from external suggestions and apply appropriate scrutiny.
  • Implementation order discipline: prioritize blocking issues, small fixes, and complex changes in a safe, testable sequence.

Quick Start

When you receive code-review feedback, follow the six-step response pattern before making changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback before implementing changes?

Evaluate code review feedback by applying a structured workflow: read, understand, verify against the codebase, evaluate risks, respond with reasoning, and implement incrementally. This ensures changes are correct and justified.

What is the best way to push back on pull request comments?

Push back on pull request comments by verifying the suggestion against your codebase and evaluating potential risks. Halt and ask clarifying questions if feedback is ambiguous before responding with technical reasoning.

How should I prioritize implementing fixes from a code review?

Prioritize code review fixes by addressing blocking issues first, followed by small fixes, and then complex changes. Implement one change at a time in a safe, testable sequence to maintain technical integrity.

How do I handle code review feedback from external contributors versus trusted partners?

Distinguish external suggestions from trusted partner feedback and apply appropriate scrutiny. External code review feedback requires stricter evaluation and verification against the codebase before implementation.

When should I ask clarifying questions during a code review?

Ask clarifying questions during a code review when any feedback item is ambiguous. Halt the evaluation workflow immediately if you do not fully understand the requirements or suggested changes before proceeding.

Does this structured code review response pattern work for multi-language codebases?

Yes, the structured code review response pattern applies to multi-language codebases and collaborative software projects with pull requests. It enforces deterministic review steps to ensure technical integrity across different environments.