receiving-code-review

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

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/csim-sg/yacc --skill receiving-code-review-csim-sg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/csim-sg/yacc/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/csim-sg/yacc --skill receiving-code-review-csim-sg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers handle code review feedback with technical rigor before implementing changes, reducing blind agreements and ensuring requirements are validated against the codebase.

Core Features & Use Cases

  • Structured feedback handling: read, understand, verify, and respond before acting.
  • Clarification and pushback: restate requirements or request details when unclear.
  • Incremental implementation: apply feedback one item at a time and verify each change.
  • Applicable across PR reviews, ticket reviews, and pair-programming sessions to ensure technically sound outcomes.

Quick Start

Follow these steps when you receive feedback:

  1. Read the feedback completely without reacting.
  2. Understand: restate the requirement or ask for clarification.
  3. Verify: compare the feedback against the codebase and tests.
  4. Evaluate: judge whether the suggestion is technically correct for THIS codebase.
  5. Respond: provide a technical acknowledgment or reasoned pushback.
  6. Implement: address items one by one and test each 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 before implementing pull request changes?

Process code review feedback by following a six-step pattern: read, understand, verify, evaluate, respond, and implement. This ensures you validate requirements against the codebase before making incremental changes.

What is the best way to handle unclear or technically questionable code review comments?

Handle questionable code review comments by restating the requirement to ask for clarification, verifying the suggestion against the codebase, and providing a reasoned technical pushback before implementing any changes.

How do I ensure technical rigor when addressing pull request feedback?

Ensure technical rigor during pull requests by comparing feedback against existing tests, evaluating if the suggestion is correct for your specific codebase, and addressing items one by one with testing after each change.

When should I push back on code review suggestions?

Push back on code review suggestions after verifying the feedback against the codebase and evaluating its technical correctness, providing a reasoned response instead of a blind agreement when the guidance is questionable.

Can I apply structured feedback processing to pair programming and ticket reviews?

Yes, you can apply structured feedback processing across PR reviews, ticket reviews, and pair-programming sessions to validate requirements and ensure technically sound outcomes before acting.