skills.rest
mnsgrosa
mnsgrosaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Apr 25, 2026
Search Tags:#feedback#verification#quality-assurance#risk-management#code-review#pull-request
One-click install
npx skills add https://github.com/mnsgrosa/skills --skill receiving-code-review-mnsgrosa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mnsgrosa/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/mnsgrosa/skills --skill receiving-code-review-mnsgrosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review can be emotionally charged and lead to premature or misaligned changes. This Skill provides a structured, tech-focused approach to handling feedback, ensuring verification of requirements and alignment with the codebase before any modification.

Core Features & Use Cases

  • READ: complete feedback without reacting
  • UNDERSTAND: restate requirement in your own words or ask for clarification
  • VERIFY: check against the actual codebase
  • EVALUATE: determine technical correctness for THIS codebase
  • RESPOND: provide a technical acknowledgment or reasoned pushback
  • IMPLEMENT: tackle items one at a time, with testing

Quick Start

When you receive code review feedback, begin by reading the comments fully, restate the requirement in your own words, verify against the codebase, evaluate technical correctness, respond with a reasoned pushback or acknowledgment, and implement items one at a time.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback without making unnecessary changes?▼

To respond to code review feedback safely, read comments fully, restate requirements, verify against the codebase, evaluate technical correctness, and implement changes one item at a time with testing.

What is the best way to handle ambiguous code review comments on a pull request?▼

The best way to handle ambiguous code review comments is to restate the requirement in your own words and ask for clarification before verifying the issue against the actual codebase.

How do I push back on technically incorrect code review feedback?▼

To push back on technically incorrect feedback, verify the comment against the codebase, evaluate its correctness for your specific context, and respond with a reasoned, technical acknowledgment or pushback.

What steps should I follow to implement code review changes correctly?▼

Follow a six-step workflow to implement code review changes: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT, ensuring you tackle items one at a time and run test verification.

Why do I need to verify code review feedback before implementing it?▼

You need to verify code review feedback before implementing it to ensure alignment with the actual codebase, prevent premature or misaligned changes, and maintain disciplined quality assurance.

Can I address multiple code review items at the same time?▼

No, you should tackle code review items one at a time to maintain disciplined verification, ensure technical correctness, and run test verification for each individual change.

Related Skills

Explore More Software Engineering Skills→
awinogradovawinogradov
5

pr:resolve

Analyze pull request comments, apply code fixes, and reply to reviewers via GitHub API.

Community
Advanced
GainInsightDevGainInsightDev

af-deliver-features

Implement features from approved mini-PRDs using TDD and generate pull requests.

Official
Advanced
huyhung9630huyhung9630
1

omc-verify

Verify software changes with static analysis, unit tests, integration tests, and manual checks.

Community
Advanced
crbnoscrbnos
2.3k

auth

Automate login to a local Carbon ERP dev server using a bypass email.

Official
Intermediate