skills.rest
oabdelmaksoud
oabdelmaksoudCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Clarifies code-review feedback using a structured six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.

4|Updated Feb 26, 2026
Search Tags:#feedback#communication#verification#pushback#code-review#development-workflow#technical-rigor
One-click install
npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill receiving-code-review-oabdelmaksoud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/oabdelmaksoud/Openclaw-skills-Compilations/tree/main/receiving-code-review
Command: npx skills add https://github.com/oabdelmaksoud/Openclaw-skills-Compilations --skill receiving-code-review-oabdelmaksoud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback can be unclear or technically questionable; this Skill provides a disciplined reception process that prevents performative agreement and ensures technical rigor before implementing changes.

Core Features & Use Cases

  • Structured six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to process feedback systematically.
  • Clarification-first approach: Restate requirements and ask questions when unclear to prevent misinterpretation.
  • Guardrails for quality: Push back with technical reasoning when feedback is insufficient or unsafe.

Quick Start

Review each feedback item using the six-step pattern before implementing any change.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I process code review feedback without just agreeing to every suggestion?▼

Process code review feedback using a structured six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This prevents performative agreement and ensures technical rigor by evaluating each item before implementing changes.

What is the best way to clarify unclear code review comments before making changes?▼

The best way to clarify code review comments is to restate the requirements and ask questions when feedback is unclear. This clarification-first approach prevents misinterpretation and ensures you verify technical requirements before writing any code.

How do I push back on code review feedback that seems technically unsafe?▼

Push back on unsafe code review feedback with technical reasoning. The workflow includes guardrails to evaluate feedback and safely push back when review suggestions are technically insufficient, unsafe, or lack clarity.

Do I need a specific development workflow to apply structured code review techniques?▼

No specific development workflow is required. The structured code review reception process applies across software projects to process feedback systematically, ensuring questions are asked and changes are implemented one item at a time.

Why does performative agreement happen during code reviews and how can I avoid it?▼

Performative agreement happens when developers implement requested changes without verifying technical rigor. Avoid it by applying a structured evaluation step to assess feedback quality before responding or implementing any code modifications.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
HanHan666666HanHan666666
10

receiving-code-review

Clarify code-review feedback, verify it against the codebase, and implement changes incrementally.

Community
Advanced
raybargasraybargas

Global Commenting

Enforces uniform, standard-based commenting across entire codebases and integrates with linters and static analysis tools for automated checks.

Community
Basic
mitchellfyimitchellfyi
3

dxprreview

Triage pull request review comments and implement scoped fixes.

Community
Advanced