skills.rest
qq824045252-ship-it
qq824045252-ship-itCOMMUNITY
Explore all skills by this author →
GitHub

superpowers-receiving-code-review

Evaluate code-review feedback against the repository before implementing changes.

Updated Apr 23, 2026
Search Tags:#communication#software-development#pushback#code-review#engineering-process#technical-verification
One-click install
npx skills add https://github.com/qq824045252-ship-it/erp --skill superpowers-receiving-code-review-qq824045252-ship-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: superpowers-receiving-code-review
Source: https://github.com/qq824045252-ship-it/erp/tree/main/.agents/skills/superpowers-receiving-code-review
Command: npx skills add https://github.com/qq824045252-ship-it/erp --skill superpowers-receiving-code-review-qq824045252-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineers navigate feedback from code reviews without succumbing to performative agreement, ensuring technical rigor, clear requirements, and incremental, testable changes.

Core Features & Use Cases

  • Restate requirements to confirm understanding before acting.
  • Verify feedback against the actual codebase to avoid misinterpretations.
  • Implement changes one item at a time with validation and testing.
  • Push back with technical reasoning when feedback is unclear.

Quick Start

Summarize the feedback in your own words, validate each item against the codebase, and proceed only after technical verification.

Frequently Asked Questions about superpowers-receiving-code-review

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

FAQPage Schema
How do I handle conflicting code review feedback without just agreeing?▼

Resolve conflicting code review feedback by restating requirements to confirm understanding, verifying comments against the actual codebase, and pushing back with technical reasoning before making any changes.

What is the best way to verify unclear code review comments against my repository?▼

Verify unclear code review comments by restating the feedback in your own words, validating each item against the actual codebase, and proceeding only after technical verification confirms the issue.

How to implement code review changes incrementally with testing?▼

Implement code review changes incrementally by processing one item at a time, validating and testing each change thoroughly before moving to the next requested modification.

When should I push back on code review feedback in software development?▼

Push back on code review feedback when comments are unclear or technically inaccurate, using technical reasoning to explain your stance instead of succumbing to performative agreement.

Why does performative agreement hurt the engineering process during code reviews?▼

Performative agreement hurts the engineering process by bypassing technical rigor, leading to unverified changes, unclear requirements, and potentially flawed code modifications during reviews.

Related Skills

Explore More Software Engineering Skills→
sachio222sachio222

receiving-code-review

Processes code review feedback through a six-step verification-first workflow.

Community
Advanced
eatbreadseatbreads
1

test-driven-development

Enforce a red-green-refactor workflow with failing tests before production code.

Community
Intermediate
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
cloudfieldczcloudfieldcz
7

receiving-code-review

Clarify code-review feedback by verifying requirements against the codebase.

Official
Intermediate