receiving-code-review

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

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill receiving-code-review-lespaceman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill receiving-code-review-lespaceman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review requires technical evaluation, not emotional performance. This skill ensures feedback is processed with rigorous technical justification before implementing changes.

Core Features & Use Cases

  • READ: Read the complete feedback without reacting
  • UNDERSTAND: Restate the requirement in your own words or ask for clarification
  • VERIFY: Check against the codebase reality
  • EVALUATE: Determine technical correctness for THIS codebase
  • RESPOND: Provide technical acknowledgment or reasoned pushback
  • IMPLEMENT: Tackle items one at a time with tests
  • Handling Unclear Feedback: If any item is unclear, pause and ask for clarification before proceeding
  • Source-Specific Handling: For external feedback, verify technical correctness, consider scope, and push back when necessary
  • YAGNI & Guardrails: Avoid unnecessary changes; only implement what is required

Quick Start

Apply the six-step process to incoming code-review feedback before making 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 process code review feedback without making incorrect changes?

Process code review feedback by enforcing a rigorous technical verification workflow before any modification. This ensures changes reflect actual code reality and reduces the risk of incorrect updates across diverse codebases.

What is the best way to handle unclear feedback during a code review?

Handling unclear code review feedback requires pausing to ask for clarification before proceeding. This ensures you fully understand the requirement and avoids implementing unnecessary or incorrect modifications.

How do I push back on automated reviewer comments technically?

Push back on automated reviewer comments by applying technical verification to check feedback against codebase reality. Evaluate technical correctness for your specific context and provide documented justification for reasoned pushback.

When should I not implement changes requested in a code review?

Avoid implementing code review changes when they violate YAGNI principles or lack technical correctness for your codebase. Only implement what is required and justified by verified code reality.

Can I use this structured review workflow for feedback from human reviewers and agents?

Yes, the structured review workflow handles feedback from humans, automated reviewers, or other agents. It verifies technical correctness, considers scope, and enforces documented justification for every change.

What steps should I follow to evaluate code review comments effectively?

Follow a structured six-step workflow: READ the feedback, UNDERSTAND the requirement, VERIFY against codebase reality, EVALUATE correctness, RESPOND with acknowledgment or pushback, and IMPLEMENT changes one at a time with tests.