skills.rest
rcliment1987
rcliment1987COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code-review feedback against the codebase and implement changes incrementally with tests.

Updated Aug 27, 2026
Search Tags:#feedback#verification#clarification#best-practices#pushback#code-review
One-click install
npx skills add https://github.com/rcliment1987/skills-bimsmarter --skill receiving-code-review-rcliment1987
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/rcliment1987/skills-bimsmarter/tree/main/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/rcliment1987/skills-bimsmarter --skill receiving-code-review-rcliment1987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined approach to processing code-review feedback, ensuring technical correctness and avoiding blind agreement.

Core Features & Use Cases

  • Structured understanding: Restate requirements, verify against the codebase, and determine feasibility before acting.
  • Clear communication: Ask clarifying questions and provide reasoned pushback when needed.
  • Incremental implementation: Tackle feedback item by item, validating changes and avoiding regressions.
  • Use Case: A developer receives ambiguous feedback on a PR; use this skill to confirm requirements, push back with technical reasoning, and plan a safe, verifiable fix.

Quick Start

Follow the six-step response pattern to handle incoming code-review feedback.

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

Processing code review feedback requires identifying exact requirements, verifying feasibility against the codebase, providing reasoned pushback, and implementing changes incrementally with tests to ensure technical correctness.

What is the best way to ask for clarification on ambiguous code review comments?▼

Asking for clarification on ambiguous comments involves restating the requested requirements, evaluating potential risks and impact on the current codebase, and explicitly asking questions to confirm what is being asked before acting.

How do I push back on code review feedback with technical reasoning?▼

Pushing back with technical reasoning requires evaluating the incoming feedback against the current codebase to determine feasibility and risks, then providing technically grounded responses that prioritize blocking issues before implementation.

How do I implement code review changes incrementally to avoid regressions?▼

Implementing changes incrementally involves tackling feedback item by item, prioritizing blocking issues first, validating each change with tests, and avoiding regressions by confirming requirements before modifying code.

Related Skills

Explore More Software Engineering Skills→
bbohhu-progbbohhu-prog

receiving-code-review

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

Community
Intermediate
g4rcezg4rcez
48

refactor

Refactor codebases by extracting functions and renaming variables while preserving behavior.

Community
Intermediate
jagreehaljagreehal
3

code-review-reception

Validate code review feedback against the codebase before incremental implementation.

Community
Basic
SuperCorksSuperCorks

address-pr-comments

Fetch GitHub PR reviews via gh CLI and apply latest reviewer feedback.

Community
Advanced