receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: enigmaicon-eng

Verify code review feedback against the codebase before implementing changes.

1|Updated May 16, 2026

Search Tags:#code review #pull request #github #verification #clarification #yagni #implementation order

Ready to run

npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill receiving-code-review-enigmaicon-eng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill receiving-code-review-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect or unsafe changes caused by blindly accepting code review feedback, especially when feedback is unclear, technically questionable, or conflicts with existing codebase realities.

Core Features & Use Cases

Structured response workflow: Read, understand, verify, evaluate for the specific codebase, respond, then implement one item at a time.
Clarification-first handling: Stops progress when any feedback item is unclear, asks targeted questions, and avoids partial implementation.
Skeptical but rigorous external review stance: Checks for breakage risk, platform/version compatibility, true usage (YAGNI), and conflicts with prior decisions.

Quick Start

Use this Skill when you receive a pull request or inline comment and want to respond with technical rigor by verifying the suggestion against the codebase 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 verify code review feedback before implementing changes?▼

To verify code review feedback, read and understand the suggestion, then evaluate it against your specific codebase for breakage risk, platform compatibility, and true usage before implementing one item at a time.

What should I do when a pull request review comment is unclear or conflicting?▼

When pull request review feedback is unclear or conflicting, stop progress immediately and ask targeted clarifying questions. Avoid partial implementation until the technical suggestion is fully understood and verified.

How do I handle multiple items in a GitHub pull request review thread?▼

Handle multiple GitHub pull request review items by responding to and implementing them incrementally, one at a time. Evaluate each suggestion individually for correctness and YAGNI compliance before proceeding to the next.

Why should I be skeptical of code review suggestions on my pull request?▼

You should be skeptical of code review suggestions because feedback may be technically questionable or conflict with existing codebase realities. Enforcing skepticism prevents incorrect, unsafe changes, and forbids performative approval.

Can I use this workflow for inline GitHub comment replies on my codebase?▼

Yes, you can use this workflow for inline GitHub comment replies. It applies to inline comments and multi-item PR review threads, enforcing technical verification and clarification-first stopping for your specific codebase.