skills.rest
cpp-for-everything
cpp-for-everythingOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Guide developers through a six-step code-review feedback process with verification.

1|Updated Mar 8, 2024
Search Tags:#communication#verification#risk-management#code-review#pull-request#technical-clarity
One-click install
npx skills add https://github.com/cpp-for-everything/ORM --skill receiving-code-review-cpp-for-everything
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/cpp-for-everything/ORM/tree/main/.windsurf/skills/receiving-code-review
Command: npx skills add https://github.com/cpp-for-everything/ORM --skill receiving-code-review-cpp-for-everything

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often arrives emotionally or ambiguously. This Skill guides you to verify requirements, restate needs, and push back with technical justification before acting.

Core Features & Use Cases

  • Structured interpretation of feedback before changes.
  • Verify against the codebase and test assumptions; implement one item at a time.
  • Handle unclear feedback by requesting clarification and logging rationale.

Quick Start

Use when you receive feedback to read, restate, verify, evaluate, respond technically, and implement one item 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 manage code review feedback without getting defensive?▼

Manage code review feedback by restating requirements, verifying against the codebase, and responding with technical justification before implementing. This enforces a non-emotional, structured approach to communication and risk-management during pull-request reviews.

What is the process for verifying pull-request feedback before making changes?▼

Verifying pull-request feedback requires a six-step process: read, restate, verify against the codebase, evaluate, respond with technical justification, and implement one item at a time. This ensures technical clarity and prevents acting on ambiguous or invalid review comments.

How should I respond to ambiguous code review comments?▼

Handle ambiguous code review comments by requesting clarification and logging the rationale before implementation. This enforces clear guardrails for unclear items, ensuring you verify assumptions and push back technically rather than guessing at requirements.

Can I apply this code review process across different programming languages?▼

Yes, you can apply this code review process across all languages and projects because it focuses on communication and risk-management rather than language-specific syntax. It ensures technical clarity and verification regardless of the codebase's underlying technology stack.

Why implement pull-request feedback one item at a time?▼

Implementing pull-request feedback one item at a time enforces rigorous risk-management and technical clarity. This structured approach allows developers to verify each requirement against the codebase and provide technical justification for individual changes before moving forward.

Related Skills

Explore More Software Engineering Skills→
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
family3253family3253

superpowers-receiving-code-review

Validate code-review feedback against the codebase before implementing changes.

Community
Intermediate
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
rafaelromaorafaelromao
5

sandman-pr-review

Automate GitHub Pull Request review loops with the gh CLI.

Community
Intermediate