skills.rest
HumanBean17
HumanBean17COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify incoming code review feedback against codebase constraints before implementation.

8|1|Updated Apr 20, 2026
Search Tags:#code review#pull request#refactoring#verification#technical rigor#engineering
One-click install
npx skills add https://github.com/HumanBean17/jrag --skill receiving-code-review-humanbean17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/HumanBean17/jrag/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/HumanBean17/jrag --skill receiving-code-review-humanbean17

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: Enforces a strict process of reading, understanding, verifying, and evaluating feedback before taking action.
  • Technical Pushback: Provides a framework for questioning or pushing back on feedback that is technically incorrect, breaks existing functionality, or violates YAGNI principles.
  • Use Case: When a reviewer suggests a complex refactor that might break legacy compatibility, this skill guides you to verify the impact, ask clarifying questions, and provide reasoned technical pushback instead of blindly accepting the suggestion.

Quick Start

Apply the receiving code review protocol to the current pull request feedback to verify each item before 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 verify code review feedback before implementing changes?▼

Verify code review feedback by reading, understanding, and evaluating it against existing codebase constraints and project requirements before taking any implementation action. This prevents performative agreement and ensures technical correctness.

What is the best way to push back on incorrect pull request feedback?▼

Push back on incorrect pull request feedback by using a structured framework that prioritizes technical reasoning over performative agreement. Validate the suggestion against existing functionality and provide reasoned technical pushback if it violates constraints.

When should I reject a refactoring suggestion during a code review?▼

Reject a refactoring suggestion during a code review when it breaks existing functionality, violates YAGNI principles, or compromises legacy compatibility. Always verify the technical impact of the refactor against the codebase before accepting.

How do I avoid blind implementation of peer feedback in software engineering?▼

Avoid blind implementation of peer feedback by applying a strict verification workflow that standardizes the evaluation process. Ensure all external input is technically verified against codebase constraints and architectural alignment before making changes.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
JylhisJylhis
1

golang-security

Detect Go vulnerabilities using govulncheck, static analysis, and DREAD scoring.

Community
Advanced
chokky-educationchokky-education

receiving-code-review

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

Community
Intermediate