skills.rest
robertpelloni
robertpelloniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Process code-review feedback by verifying technical soundness and implementing changes one item at a time with tests.

2|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/robertpelloni/workspace --skill receiving-code-review-robertpelloni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/robertpelloni/workspace/tree/main/AI_COORDINATION/skills/superpowers-skills-main/skills/collaboration/receiving-code-review
Command: npx skills add https://github.com/robertpelloni/workspace --skill receiving-code-review-robertpelloni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers efficiently process and act upon code review feedback, ensuring that suggestions are understood, implemented correctly, and that the review cycle is completed promptly. It reduces miscommunication and rework.

Core Features & Use Cases

  • Feedback Interpretation: Clarify ambiguous comments and understand the intent behind suggestions.
  • Action Planning: Generate a plan to address all review comments systematically.
  • Use Case: After receiving a code review, use this skill to analyze the feedback, prioritize changes, and generate a step-by-step plan for implementing the requested modifications.

Quick Start

Review the feedback in the attached 'review_comments.md' and suggest a plan to address them.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I systematically address code review feedback to avoid rework?▼

Code review feedback should be read fully, restated to confirm understanding, verified against your codebase, and evaluated for technical soundness before implementation. Address feedback one item at a time with tests to ensure correctness and reduce miscommunication cycles.

What should I do when code review comments are unclear or technically questionable?▼

When feedback is ambiguous or technically unclear, restate the requirement back to the reviewer, verify it against your codebase context, and provide reasoned technical acknowledgment or pushback with evidence. This clarifies intent before implementing changes.

How do I plan implementation of multiple code review suggestions?▼

Generate a step-by-step plan that prioritizes all review comments systematically. Break implementation into single items with testing for each to ensure each change is correct before moving to the next feedback item.

Can I implement code review changes incrementally with testing?▼

Yes. Implementing feedback one item at a time with tests for each change reduces risk, catches errors early, and makes it easier to isolate which change caused a problem if issues arise during the review cycle.

What's the best way to respond to code review feedback I disagree with?▼

Provide technical acknowledgment with reasoned pushback grounded in your codebase context. Reference specific code, performance implications, or architectural reasons why the suggestion may not apply, allowing the reviewer to reconsider informed by your evidence.

Related Skills

bkelly-labbkelly-lab
50

verify-review

Parse PR review feedback and validate subsequent commits against checklist items.

Official
Advanced
mvillmowmvillmow
18

gh-fix-pr-feedback

Fetch GitHub PR review comments, implement changes, and reply to each comment.

Community
Basic
elijahmurrayelijahmurray
2

pr-review

Check out pull request branches, review code changes, and apply feedback.

Community
Basic
pulzzepulzze

interactor-workflows

Automate state-machine workflows with human-in-the-loop approvals using Interactor.

Official
Intermediate