receiving-code-review

Evaluate code review feedback against the codebase before implementation.

2|Updated Apr 24, 2026

Search Tags:#code review #feedback #refactoring #verification #technical rigor #pushback

Ready to run

npx skills add https://github.com/LisztVan/subcli-cpp --skill receiving-code-review-lisztvan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/LisztVan/subcli-cpp/tree/main/.pi/skills/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/LisztVan/subcli-cpp --skill receiving-code-review-lisztvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle code review feedback with technical rigor instead of reflexive agreement, so you can avoid implementing unclear or incorrect suggestions.

Core Features & Use Cases

Verify Before Acting: Check each review comment against the actual codebase before making changes.
Clarify Ambiguity: Identify unclear items early and ask targeted questions before implementation begins.
Reasoned Pushback: Push back when a suggestion conflicts with existing architecture, platform constraints, or working behavior.
Incremental Fixes: Apply changes one item at a time and verify each step to avoid regressions.
Use Case: A reviewer asks for several changes in one thread, but one item is ambiguous and another would break compatibility; this Skill helps you sort, verify, and respond correctly.

Quick Start

Paste the review comments into the Skill and ask it to verify each point against the codebase before drafting any implementation plan.

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, check each comment against the actual codebase to confirm validity, clarify ambiguous items early, and push back when suggestions conflict with existing architecture or platform constraints.

What should I do when a code review comment is unclear or ambiguous?▼

When a code review comment is ambiguous, identify the unclear items early and ask targeted questions before implementation begins to avoid applying incorrect or unnecessary changes to the active codebase.

How to push back on code review suggestions that break compatibility?▼

To push back on incompatible code review suggestions, reason against the existing stack and platform constraints, verifying that the requested change would break working behavior before drafting a technical response.

What is the best way to handle multiple code review items in one thread?▼

The best way to handle multiple code review items is to sort, verify each point individually against the repository, and apply incremental one-at-a-time fixes with testing to avoid regressions.

When should I not implement a requested change from a code reviewer?▼

You should not implement a requested change when the suggestion conflicts with existing architecture, platform constraints, or working behavior, requiring reasoned pushback instead of reflexive agreement.

Does receiving-code-review work with existing platform constraints and architectural tradeoffs?▼

Yes, receiving-code-review evaluates externally sourced comments by verifying them against repository reality, specifically handling platform constraints and architectural tradeoffs through reasoned pushback and incremental fixes.