receiving-code-review

Verify and implement code review feedback through a structured six-step workflow.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill receiving-code-review-herxinsasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill receiving-code-review-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of unprofessional, unverified responses to code review feedback that lead to unnecessary code changes, introduced bugs, or wasted development effort, replacing performative agreement and blind implementation with a structured, technically rigorous process.

Core Features & Use Cases

  • Structured 6-Step Response Workflow: A repeatable process (read, understand, verify, evaluate, respond, implement) to ensure all feedback is fully assessed before taking action.
  • Scenario-Specific Guidance: Clear rules for handling unclear feedback, feedback from external reviewers versus human partners, YAGNI checks for unnecessary feature requests, and reasoned pushback for technically incorrect suggestions.
  • Best Practice Templates: Concrete examples of correct responses for acknowledging valid feedback, correcting mistaken pushback, and replying to GitHub inline review comments.
  • Use Case: When a reviewer requests removal of legacy code, you first verify if it is required for backward compatibility instead of immediately agreeing, avoiding breakage for users on older supported versions.

Quick Start

Use the receiving-code-review skill to respond to the code review feedback on your latest pull request, verifying each suggestion against the codebase and project requirements before implementing any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle code review feedback without introducing unnecessary changes?

Handling code review feedback requires a structured 6-step workflow: read, understand, verify, evaluate, respond, and implement. This prevents blind implementation of suggestions by ensuring technical rigor and verifying feedback against the codebase.

What is the best way to respond to incorrect pull request review comments?

Responding to incorrect pull request comments requires reasoned pushback. Evaluate the technical suggestion against your codebase context and project requirements, then reply with a structured, technically rigorous explanation instead of performative agreement.

How do I verify a code review suggestion before implementing changes?

Verifying a code review suggestion requires checking it against the codebase and project requirements. For example, if a reviewer requests removing legacy code, first verify if it is required for backward compatibility to avoid breaking older supported versions.

When should I apply YAGNI checks to code review feedback?

Apply YAGNI checks to code review feedback when evaluating suggestions that add new features. This ensures compliance with the You Aren't Gonna Need It principle, preventing unnecessary feature requests from turning into wasted development effort and technical debt.

Does this approach work for feedback from automated tools and external reviewers?

Yes, this approach works for automated tools and external reviewers by applying scenario-specific guidance. It provides clear rules for handling feedback from external reviewers versus human partners, ensuring context-aware verification regardless of the source.