skills.rest
duongbui234
duongbui234COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluates code review feedback and implements verified changes with reasoned technical responses.

Updated May 9, 2026
Search Tags:#refactoring#verification#code-review#pull-request#technical-rigor#engineering-standards
One-click install
npx skills add https://github.com/duongbui234/ag-skills-pro --skill receiving-code-review-duongbui234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/duongbui234/ag-skills-pro/tree/main/template/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/duongbui234/ag-skills-pro --skill receiving-code-review-duongbui234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation of feedback, ensuring that code reviews remain focused on technical correctness and architectural integrity.

Core Features & Use Cases

  • Verification-First Workflow: Mandates checking feedback against codebase reality before implementation.
  • Technical Pushback: Provides a structured framework for challenging incorrect or context-blind suggestions.
  • Use Case: When an external reviewer suggests a refactor that breaks backward compatibility or violates YAGNI, this skill guides the agent to verify the claim and provide a reasoned technical rebuttal instead of blindly accepting the change.

Quick Start

Invoke the receiving-code-review skill to evaluate the pending feedback on the current pull request and prepare a technically verified response.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle code review feedback without blindly implementing it?▼

To handle code review feedback without blind implementation, evaluate suggestions against codebase constraints and architectural decisions before applying changes. This verification-first approach ensures technical correctness over performative agreement.

What is performative agreement in code reviews?▼

Performative agreement in code reviews occurs when developers accept peer feedback without objective evaluation, leading to blind implementation that may break backward compatibility or violate YAGNI principles.

How do I push back on an incorrect pull request review suggestion?▼

To push back on an incorrect pull request review suggestion, verify the claim against codebase reality and provide a reasoned technical rebuttal instead of accepting the change. This structured framework maintains architectural integrity.

When should I challenge a refactoring suggestion from a peer reviewer?▼

You should challenge a refactoring suggestion when it breaks backward compatibility, violates YAGNI, or ignores existing codebase constraints. Address questionable suggestions through reasoned technical discourse rather than performative agreement.

How do I verify technical feedback before applying changes to a codebase?▼

To verify technical feedback before applying changes, validate external review comments against existing architectural decisions and test all implemented changes individually. This maintains engineering standards during the pull request workflow.

Related Skills

Explore More Software Engineering Skills→
chokky-educationchokky-education

receiving-code-review

Standardizes incoming code review feedback verification and technical response preparation for pull requests and peer sessions.

Community
Intermediate
PlazaCCPlazaCC
2

receiving-code-review

Verify code review feedback and plan implementation steps.

Official
Intermediate
gkganesh12gkganesh12
1

gk-review

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

Community
Advanced
manuelbrandner85manuelbrandner85

receiving-code-review

Evaluates code review feedback by verifying it against the codebase.

Community
Intermediate