skills.rest
chokky-education
chokky-educationCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Feb 24, 2026
Search Tags:#code review#collaboration#pull request#refactoring#software quality#technical rigor
One-click install
npx skills add https://github.com/chokky-education/science-club-web --skill receiving-code-review-chokky-education
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/chokky-education/science-club-web/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/chokky-education/science-club-web --skill receiving-code-review-chokky-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Verification Workflow: Provides a structured, step-by-step process to evaluate feedback for technical correctness and project context.
  • Pushback Guidance: Offers clear strategies for challenging suggestions that violate YAGNI, break functionality, or conflict with architectural decisions.
  • Use Case: When an external reviewer suggests a complex refactor that is unnecessary for the current project scope, this skill guides you to verify the actual usage of the code and push back with technical reasoning rather than agreeing out of social pressure.

Quick Start

Use the receiving-code-review skill to evaluate the latest pull request feedback by following the verification steps and preparing a technical 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 evaluate code review feedback before implementing changes?▼

Push back on code review suggestions by verifying the actual code usage and formulating technical reasoning. This approach challenges feedback violating YAGNI or breaking functionality, avoiding performative agreement driven by social pressure.

What is the best way to respond to unnecessary refactoring suggestions in a pull request?▼

Handle unnecessary refactoring suggestions by verifying the current project scope and code usage. Respond with technical reasoning that justifies pushing back against complex refactors that conflict with architectural decisions or violate YAGNI principles.

How do I prepare a technical response to peer review feedback?▼

Use receiving-code-review to evaluate the latest pull request feedback by following the verification steps. It applies to pull request interactions, external contributor suggestions, and peer review sessions to maintain technical rigor.

When should I not implement code review feedback directly?▼

Do not implement feedback directly when suggestions break functionality, violate YAGNI, or conflict with architectural decisions. Blind implementation is prevented by requiring systematic verification against the codebase before any changes are made.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
FaisalAlqarniFaisalAlqarni
5

springboot-verification

Automate build, static analysis, testing, and security scanning for Spring Boot projects.

Community
Advanced
NagyViktNagyVikt
2

receiving-code-review

Evaluate code review feedback for technical correctness and architectural integrity.

Community
Intermediate