skills.rest
fernandoxavier02
fernandoxavier02COMMUNITY
Explore all skills by this author →
GitHub

superpower-receiving-code-review

Verify code-review feedback against codebase scope and constraints before implementing.

Updated Aug 23, 2026
Search Tags:#verification#quality-assurance#code-review#pull-request#technical-rigor#feedback-analysis
One-click install
npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-receiving-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: superpower-receiving-code-review
Source: https://github.com/fernandoxavier02/Codex-superpower/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often contain ambiguities or unfinished reasoning. This Skill ensures you verify and reason technically before implementing feedback, reducing blind agreement and risky changes.

Core Features & Use Cases

  • Restate the exact requirement from feedback to confirm understanding.
  • Verify alignment with the codebase, current scope, and project constraints before acting.
  • Push back with technical reasoning when feedback is unclear or incorrect, and implement changes step by step with validation.

Quick Start

Restate the technical requirement, verify it against the codebase, and implement only after validation.

Frequently Asked Questions about superpower-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, you must restate the technical requirement, check alignment with the codebase and project scope, and validate the proposed changes to ensure they are justified and isolated to prevent regressions.

Why should I analyze code review feedback before acting on it?▼

Analyzing feedback prevents blind agreement with ambiguous or unfinished reasoning found in code reviews. It enforces technical rigor to ensure modifications align with project constraints and avoid risky regressions.

What is the best way to handle ambiguous pull request feedback?▼

Handling ambiguous pull request feedback requires restating the requirement to confirm understanding, verifying it against the codebase, and pushing back with technical reasoning if the feedback remains unclear or incorrect.

Can I push back on code review comments if they lack technical rigor?▼

Yes, you can push back on code review comments when feedback is unclear or incorrect. You should provide technical reasoning and implement changes step by step only after validation against the current project constraints.

How do I ensure code review changes do not introduce regressions?▼

To avoid regressions, verify that code review changes are justified, tested, and isolated. Confirm the feedback aligns with the current scope and constraints before proceeding with step-by-step implementation.

Related Skills

Explore More Software Engineering Skills→
edlngedlng
2

pr-comment-humanizer

Rewrite pull request review comments into terse, imperative engineering tone.

Community
Intermediate
SimpleEveSimpleEve
30

eo-test

Validate code changes with automated unit and integration tests and generate a test.md report.

Community
Intermediate
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
HanHan666666HanHan666666
10

receiving-code-review

Clarify code-review feedback, verify it against the codebase, and implement changes incrementally.

Community
Advanced