skills.rest
rafifos
rafifosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Process code-review feedback using a six-step verification workflow.

6|Updated Mar 24, 2019
Search Tags:#debugging#communication#quality-assurance#code-review#pull-request#technical-verification
One-click install
npx skills add https://github.com/rafifos/dotfiles --skill receiving-code-review-rafifos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/rafifos/dotfiles/tree/main/dot_agents/skills/receiving-code-review
Command: npx skills add https://github.com/rafifos/dotfiles --skill receiving-code-review-rafifos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid blindly agreeing to feedback by enforcing a structured, technically rigorous approach to code reviews.

Core Features & Use Cases

  • Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT
  • Handling unclear feedback: STOP and ask for clarification
  • Source-specific handling for external reviewers and human partner rules
  • YAGNI checks and guardrails
  • One-at-a-time implementation with test verification

Quick Start

Read the feedback, restate the requirement in your own words, verify it against the codebase, and implement changes one item at a time after confirmation.

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 blindly agreeing to changes?▼

To process code review feedback without blindly agreeing, apply a structured verification workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces technical rigor by verifying guidance against the codebase before implementation.

What is the best way to handle ambiguous or unclear code review comments?▼

Handling ambiguous code review comments requires you to stop and ask for clarification. Restate the requirement in your own words and verify it against the codebase before proceeding with any implementation.

How do I implement pull request changes one item at a time?▼

Implement pull request changes one item at a time by evaluating each feedback point individually, confirming the requirement, and applying incremental, verifiable changes with test verification after each step.

When should I ask for clarification during a code review?▼

You should ask for clarification during a code review whenever feedback is partial, ambiguous, or misinterpreted. Stop immediately if the reviewer's guidance lacks sufficient technical context for accurate verification.

How do you apply YAGNI checks to code review feedback?▼

Apply YAGNI checks to code review feedback by evaluating whether requested changes are strictly necessary. Use guardrails to prevent over-engineering and ensure incremental modifications align with actual project requirements.

Related Skills

Explore More Software Engineering Skills→
yves-syves-s
24

receiving-code-review

Verify code review feedback against codebase context before implementing fixes.

Community
Intermediate
Smooth-OperationSmooth-Operation

verification-before-completion

Enforce a final verification gate before declaring work complete.

Official
Advanced
darelabs-techdarelabs-tech

dare-review

Audit software task implementations against technical specifications for DARE methodology compliance.

Official
Advanced
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced