skills.rest
Ehrax
EhraxCOMMUNITY
Explore all skills by this author →
𝕏@0xEhraxGitHub

receiving-code-review

Respond to code review feedback using a six-step verification-first workflow.

Updated Feb 11, 2016
Search Tags:#workflow#verification#pushback#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/Ehrax/dotfiles --skill receiving-code-review-ehrax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/receiving-code-review
Command: npx skills add https://github.com/Ehrax/dotfiles --skill receiving-code-review-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often ambiguous or technically questionable. This skill provides a structured, verifiable approach to receiving feedback, ensuring changes are justified and backed by codebase reality.

Core Features & Use Cases

  • Structured six-step response pattern (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to feedback.
  • Guardrails against performative agreement and risky changes; require clarifications and technical validation.
  • Handling unclear feedback: ask for clarification before proceeding; push back with reasoned technical arguments.

Quick Start

Clarify ambiguous feedback, verify requirements against the codebase, and implement changes incrementally only after technical validation.

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 ambiguous code review feedback on a pull request?▼

Handle ambiguous code review feedback by using a structured verification-first approach to clarify unclear items before implementation. This involves reading, understanding, and verifying the requested changes against the codebase to ensure technical justification.

What is the best way to push back on technically questionable code review comments?▼

Push back on technically questionable code review comments by validating the requirements against the repository first. A structured workflow ensures you evaluate feedback technically, allowing you to respond with reasoned arguments instead of performative agreement.

How do I verify code review requirements against my codebase before making changes?▼

Verify code review requirements against your codebase by following a six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This process ensures explicit codebase verification occurs before you plan safe, incremental modifications.

When should I ask for clarification on code review feedback instead of implementing it?▼

Ask for clarification on code review feedback when items are unclear or technically questionable. You should request clarification before proceeding to ensure changes are justified, backed by codebase reality, and avoid risky modifications.

Can I implement code review changes incrementally after technical validation?▼

Yes, you can implement code review changes incrementally after technical validation. A structured workflow ensures you plan safe modifications only after verifying requirements against the repository and evaluating the feedback.

Related Skills

Explore More Software Engineering Skills→
przbaduprzbadu
1

pr-review-fixer

Extract and validate GitHub pull request review comments before applying code fixes.

Community
Advanced
ilderajilderaj

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Advanced
EpiphyticEpiphytic
7

receiving-code-review

Evaluate code review feedback before implementing suggested changes.

Official
Intermediate
databrickslabsdatabrickslabs
38

receiving-code-review

Evaluate code review feedback with structured verification and YAGNI checks.

Official
Intermediate