receiving-code-review

Verify code review feedback against the codebase before merging changes.

8|1|Updated Jan 24, 2026

Search Tags:#verification #quality-assurance #code-review #root-cause-analysis #pull-request #systemic-check

Ready to run

npx skills add https://github.com/bordenet/superpowers-plus --skill receiving-code-review-bordenet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/receiving-code-review
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill receiving-code-review-bordenet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams process code review feedback with technical rigor, preventing blind implementations and ensuring changes address root causes.

Core Features & Use Cases

Verify feedback against the codebase before applying changes.
Extract underlying goals from comments and push back when requirements are unclear or technically questionable.
Implement changes incrementally, testing each item and performing a systemic check after all items are done.

Quick Start

Read the reviewer feedback, verify it against the codebase, and implement changes one by one only after confirming the underlying goal and performing the systemic verification.

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 before merging a pull request?▼

Process code review feedback by verifying suggested changes against the codebase first, extracting underlying goals from comments, and implementing fixes incrementally. This prevents blind implementations and ensures changes address root causes rather than just symptoms before merging.

What is systemic verification in pull request reviews?▼

Systemic verification in pull request reviews is a gate that enforces searching for other instances of the same pattern after applying fixes. It ensures changes are validated through incremental testing and prevents isolated patches when a broader root-cause fix is required.

How do I handle unclear or contradictory code review comments?▼

Handle unclear or contradictory code review comments by extracting their underlying goals and pushing back when requirements are technically questionable. Verify the feedback against the codebase before implementing changes to ensure the requested edits align with actual system needs.

When do I need root-cause analysis for code review feedback?▼

You need root-cause analysis for code review feedback when comments require systemic fixes rather than simple edits. If feedback points to a pattern that might exist elsewhere in the codebase, perform a systemic check to find and fix all instances before merging.

How do I verify code review changes against an existing codebase?▼

Verify code review changes against an existing codebase by applying feedback incrementally, testing each item individually, and performing a final systemic check. This ensures the underlying goal of the feedback is met without introducing regressions before merging.

Can I push back on code review feedback if the requirements are unclear?▼

Yes, you can push back on code review feedback when requirements are unclear or technically questionable. Extract the underlying goal from the comment, verify it against the codebase, and request clarification before implementing changes to avoid blind edits.