receiving-code-review

Enforce a verification-first six-step workflow for code review feedback.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Itzalive/resistance-ai --skill receiving-code-review-itzalive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Itzalive/resistance-ai/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/Itzalive/resistance-ai --skill receiving-code-review-itzalive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often leads to performative agreement or rushed changes. This Skill provides a disciplined, verification-first approach to interpret and act on feedback, ensuring changes are technically correct and aligned with the codebase.

Core Features & Use Cases

  • Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT steps to handle feedback methodically.
  • Unclear feedback handling: If any item is unclear, stop and request clarification before proceeding.
  • Source-specific handling: Distinguish between trusted human feedback and external reviewers; push back with technical reasoning when appropriate.
  • Guardrails for changes: Follow implementation order and guardrails to reduce regressions.

Quick Start

When you receive code review feedback, apply the six-step response pattern in order and verify each item before implementing.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I manage code review feedback without rushing into changes?

Manage code review feedback by applying a structured six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces a verification-first workflow, ensuring changes are technically correct and aligned with the codebase.

What is the best way to handle unclear comments on a pull request?

Handling unclear pull request comments requires stopping the workflow immediately to request clarification. A verification-first approach ensures you never assume intent, preventing performative agreement and technically incorrect modifications.

Can I push back on code review feedback from external reviewers?

Yes, you can push back on code review feedback from external reviewers by applying source-specific handling. The workflow distinguishes between trusted human feedback and external sources, allowing pushback with technical reasoning when appropriate.

How do I evaluate code review comments before modifying code?

Evaluate code review comments by verifying each item against the codebase during the EVALUATE step. This structured interpretation phase happens after UNDERSTAND and before RESPOND, ensuring you assess technical accuracy prior to any implementation.

Does a structured code review workflow prevent regressions?

A structured code review workflow prevents regressions by enforcing guardrails for changes and following a strict implementation order. By verifying feedback before acting, it ensures modifications are technically correct and aligned with existing codebase behavior.

When should I request clarification during a code review?

Request clarification during a code review immediately when any feedback item is unclear. The verification-first workflow mandates stopping the process to resolve ambiguities before proceeding to evaluation or planning any incremental changes.