skills.rest
tomasbasso
tomasbassoCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Apr 25, 2026
Search Tags:#verification#pushback#code-review#software-engineering#process-improvement#feedback-management
One-click install
npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill receiving-code-review-tomasbasso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/tomasbasso/SistemaStockV2/tree/main/.agents/skills/gestion-comentarios-revision-codigo
Command: npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill receiving-code-review-tomasbasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides technicians to handle code review feedback with discipline, ensuring requirements are verified before changes are made and avoiding blind agreement.

Core Features & Use Cases

  • Robust uptake of feedback by restating requirements, verifying against the codebase, and providing technical reasoning when necessary.
  • Structured response pattern (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to ensure consistent, safe decisions.
  • Clear handling of unclear feedback with a halt for clarification to prevent incorrect changes and misaligned scope.

Quick Start

Follow the six-step response workflow to respond to new code-review feedback before implementing any 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 handle code review feedback without blindly implementing changes?▼

To handle code review feedback safely, verify requirements against the codebase and apply technical reasoning before implementation. This prevents blind agreement by ensuring you fully understand the scope and correctness of the requested changes before modifying the code.

What is the best way to respond to conflicting code review comments?▼

The best way to respond to conflicting code review comments is to halt for clarification. Ask clarifying questions to resolve the conflict, verify the actual requirements against the codebase, and evaluate the technical reasoning before proceeding with any implementation.

How do I manage unclear feedback during a software engineering code review?▼

To manage unclear feedback during a software engineering code review, you must halt the process and ask clarifying questions. This prevents incorrect changes and scope misalignment by ensuring verified understanding before any code modifications are implemented.

What steps should I follow to evaluate code review feedback correctly?▼

To evaluate code review feedback correctly, follow a six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This structured workflow ensures consistent, safe decisions by verifying requirements against the codebase before acting.

When should I pushback on code review suggestions?▼

You should pushback on code review suggestions after verifying the requirements against the codebase and providing technical reasoning. If feedback is unclear, conflicting, or technically unsound, halt for clarification and evaluate the suggestion before implementing it.

Related Skills

Explore More Software Engineering Skills→
obraobra
41

Code Review Reception

Evaluate and implement code review feedback with technical verification.

Community
Basic
Syedyasir001Syedyasir001

requesting-code-review

Automate code review requests and dispatch reviewer subagents.

Community
Advanced
devswapnil1995devswapnil1995

monitor-ci

Monitors Nx Cloud CI pipeline builds and coordinates self-healing recovery workflows.

Community
Advanced
rafaelromaorafaelromao
5

sandman-pr-review

Automate GitHub Pull Request review loops with the gh CLI.

Community
Intermediate