skills.rest
LISANG3
LISANG3COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback against codebase reality and architecture.

1|Updated Feb 13, 2026
Search Tags:#code review#feedback#development workflow#verification#technical rigor#pushback
One-click install
npx skills add https://github.com/LISANG3/Larj --skill receiving-code-review-lisang3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/LISANG3/Larj/tree/main/skills/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/LISANG3/Larj --skill receiving-code-review-lisang3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified before implementation, preventing blind acceptance of potentially incorrect or contextually inappropriate suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers developers to critically assess feedback against codebase reality.
  • Reasoned Pushback: Facilitates constructive technical dialogue rather than performative agreement.
  • Use Case: When an external reviewer suggests a change that seems to conflict with existing architecture or requirements, this Skill guides you to verify its impact and push back with technical reasoning if necessary.

Quick Start

Use the receiving-code-review skill to evaluate feedback from an external reviewer before implementing any changes.

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 against existing architecture?▼

To verify code review feedback, evaluate the suggestions against codebase reality, existing functionality, and architectural decisions before implementation. This ensures technical rigor by confirming the changes align with project context rather than blindly accepting them.

What is the best way to push back on incorrect code review comments?▼

The best way to push back on code review comments is to facilitate constructive technical dialogue with reasoned technical arguments. Evaluate the feedback for correctness against the codebase and respond with technical reasoning rather than performative agreement.

When should I reject code review suggestions from external reviewers?▼

Reject code review suggestions when they conflict with existing architecture or requirements. Evaluate the impact of external feedback against project context and push back if the changes compromise technical correctness or adherence to codebase reality.

How do I manage code review feedback without social compliance?▼

Manage code review feedback by prioritizing technical rigor over social compliance. Technically evaluate and verify all feedback before implementation, ensuring suggestions are checked for correctness against the codebase rather than accepted to appease the reviewer.

Do I need to evaluate internal code review feedback differently than external feedback?▼

Internal and external code review feedback do not require different evaluation processes. Apply technical verification to feedback from both sources, rigorously assessing all suggestions against codebase reality and architectural decisions before proceeding with implementation.

Related Skills

Explore More Software Engineering Skills→
Come0520Come0520

receiving-code-review

Verify code review feedback against codebase reality before implementation.

Community
Intermediate
mortenbroesbymortenbroesby
1

receiving-code-review

Validate code-review feedback against the codebase before implementing changes.

Community
Advanced
hmpshmps

receiving-code-review

Validate code-review feedback for technical correctness before implementation.

Community
Intermediate
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic