skills.rest
Ouro-labs
Ouro-labsOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Process and implement code review feedback with structured verification.

14|3|Updated May 7, 2026
Search Tags:#code quality#code review#best practices#software development#technical verification#review process#feedback handling
One-click install
npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill receiving-code-review-ouro-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Ouro-labs/ouroboros-plugins/tree/main/plugins/superpowers/vendor/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill receiving-code-review-ouro-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in systematically reviewing and addressing code review feedback, ensuring technical correctness and reducing the risk of misinterpretation or incorrect implementation.

Core Features & Use Cases

  • Technical Verification: Prompts the user to verify feedback against the codebase before implementation.
  • Response Pattern: Provides a structured response pattern for handling feedback, including understanding, verifying, and evaluating suggestions.
  • Handling Unclear Feedback: Guides the user on how to handle unclear feedback and when to seek clarification.
  • Source-Specific Handling: Offers guidance on responding to feedback from different sources, such as human partners or external reviewers.
  • YAGNI Check: Encourages the user to question the necessity of suggested features.
  • Implementation Order: Suggests a structured approach to implementing multiple feedback items.
  • When To Push Back: Instructs the user on when and how to push back on feedback if it is incorrect or not applicable.
  • Acknowledging Correct Feedback: Provides guidelines on how to acknowledge correct feedback without using performative agreement.
  • Gracefully Correcting Pushback: Offers advice on how to correct mistakes when pushback was incorrect.
  • Common Mistakes: Lists common mistakes to avoid during the code review process.
  • Real Examples: Provides examples of good and bad practices in code review feedback handling.

Quick Start

Use the receiving-code-review skill to process code review feedback for the 'feature-branch' and implement the suggested 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 systematically?▼

Handling code review feedback requires verifying suggestions against the codebase, evaluating their necessity, and implementing them in a structured order. This approach ensures technical correctness and reduces the risk of misinterpretation.

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

Handling unclear code review feedback requires asking the reviewer for clarification before making changes. This prevents incorrect implementations and ensures technical alignment with the intended suggestions.

When should I push back on code review suggestions?▼

Pushing back on code review suggestions is appropriate when feedback is technically incorrect or violates YAGNI principles. Respond with structured technical reasoning rather than performative agreement to maintain code quality.

Do I need prior software development experience to use structured feedback processing?▼

Yes, using structured code review feedback processing requires a basic understanding of coding practices and review processes. This prerequisite helps you technically verify suggestions and implement changes correctly.

How do I correct a mistake if I pushed back on valid code review feedback?▼

Correcting an incorrect pushback during a code review requires gracefully acknowledging the mistake and implementing the original suggestion. This approach avoids performative agreement and realigns with correct technical practices.

What are common mistakes to avoid when implementing code review feedback?▼

Common mistakes when implementing code review feedback include failing to verify suggestions against the codebase, using performative agreement, and skipping the YAGNI check to question the necessity of suggested features.

Related Skills

Explore More Software Engineering Skills→
liujiarui0918liujiarui0918

receiving-code-review

Guides developers through analyzing and responding to code review feedback.

Community
Intermediate
matt-rileymatt-riley
1

review-comment-resolution

Classify PR review comments and apply validated fixes to code branches.

Community
Intermediate
lxt070409lxt070409
1

requesting-code-review

Automate pre-merge code verification with security scans and quality gates.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic