skills.rest
NagyVikt
NagyViktCOMMUNITY
Explore all skills by this author →
Website𝕏@NagyViktordpGitHub

receiving-code-review

Evaluate code review feedback for technical correctness and architectural integrity.

2|Updated Mar 29, 2026
Search Tags:#refactoring#github#code-review#pull-request#development-workflow#technical-rigor
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill receiving-code-review-nagyvikt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill receiving-code-review-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation of code review feedback, ensuring that all suggestions are technically verified against the codebase before any changes are made.

Core Features & Use Cases

  • Technical Verification: Provides a structured framework to evaluate feedback for technical correctness and context-awareness.
  • Strategic Pushback: Offers clear protocols for challenging questionable or context-blind suggestions using technical reasoning.
  • Use Case: When an external reviewer suggests a refactor that breaks existing legacy compatibility, use this skill to formulate a technically sound pushback that protects the current architecture.

Quick Start

Apply the receiving code review protocol to analyze the latest pull request feedback and determine which items require clarification versus immediate implementation.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback against existing codebase constraints?▼

Avoid performative agreement by applying a structured protocol to vet all external code review suggestions. Technically verify each recommendation against legacy compatibility and architectural constraints before modifying any code.

What is the best way to push back on a pull request refactor that breaks legacy compatibility?▼

Formulate a strategic pushback against questionable pull request refactors using technical reasoning. Highlight context-blind suggestions that break legacy compatibility to protect current architectural integrity during code review.

How do I stop blindly implementing GitHub pull request suggestions?▼

Stop blindly implementing GitHub pull request suggestions by applying technical verification standards. Check every recommendation for context-awareness and codebase constraints to ensure architectural integrity before modifying development workflows.

When should I apply structured verification to code review feedback?▼

Apply structured verification to code review feedback whenever external or peer suggestions require vetting against existing constraints. Use this process during development workflows to maintain technical rigor and enforce YAGNI principles.

Does this approach to receiving code review support YAGNI principles?▼

Yes, this code review evaluation approach supports YAGNI principles by standardizing feedback verification. It ensures all implemented suggestions maintain technical correctness and align with existing codebase constraints before any refactoring occurs.

What are the limitations of performative agreement in development workflows?▼

Performative agreement in development workflows causes blind implementation of feedback, risking architectural integrity. It bypasses technical verification, ignores codebase constraints, and introduces context-blind refactoring errors into the system.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
chriswickettchriswickett

pr-fix

Apply PR review feedback as commits on a dedicated branch.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
danchamorrodanchamorro
13

code-review

Review code changes and pull request diffs for bugs, security vulnerabilities, and quality issues.

Community
Advanced