skills.rest
giosuetedeschi-spec
giosuetedeschi-specCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback against codebase constraints and project goals.

Updated Jan 12, 2026
Search Tags:#code review#pull request#technical communication#software quality#engineering standards
One-click install
npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill receiving-code-review-giosuetedeschi-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/giosuetedeschi-spec/bobu-website/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill receiving-code-review-giosuetedeschi-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative, emotional, or blind agreement during code reviews, ensuring that all feedback is verified for technical accuracy and project alignment before implementation.

Core Features & Use Cases

  • Verification Workflow: Provides a structured, step-by-step process to evaluate feedback against codebase reality and architectural requirements.
  • Strategic Pushback: Offers clear guidelines on when and how to technically challenge incorrect or context-blind suggestions.
  • Use Case: When a reviewer suggests a complex refactor that breaks existing functionality or violates YAGNI principles, this skill guides you to verify the claim and provide a reasoned, technical pushback instead of blindly accepting the change.

Quick Start

Activate the receiving-code-review skill to analyze the current pull request feedback and generate a technically rigorous response plan.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback objectively?▼

To respond to code review feedback objectively, verify the suggestion against codebase constraints and project goals before implementation. This enforces technical rigor by mandating systematic review and evidence-based evaluation instead of emotional or blind agreement.

When should I push back on a pull request review comment?▼

You should push back on a pull request review comment when feedback violates architectural requirements or breaks existing functionality. Strategic pushback involves verifying the claim and providing a reasoned, technical explanation rather than blindly accepting the change.

What is the best way to evaluate complex refactoring suggestions?▼

The best way to evaluate complex refactoring suggestions is using a structured verification workflow to check the feedback against codebase reality. This prevents performative agreement and ensures the proposed changes align with technical constraints and YAGNI principles.

How do I stop blindly agreeing to peer feedback during software development?▼

To stop blindly agreeing to peer feedback during software development, enforce a verification workflow that validates external suggestions against existing codebase logic. This ensures adherence to technical rigor by requiring clarification and evidence-based implementation.

Does this code review response approach work for all software engineering standards?▼

This code review response approach works for software engineering workflows where external or peer feedback requires validation against existing codebase constraints and project goals. It ensures adherence to technical rigor through systematic review and logical evaluation.

Why does performative agreement hurt software quality during code reviews?▼

Performative agreement hurts software quality during code reviews because it bypasses technical accuracy and project alignment. Implementing unverified feedback blindly can introduce breaking changes, making objective, technically-driven responses essential for maintaining engineering standards.

Related Skills

Explore More Software Engineering Skills→
russosalvrussosalv
5

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate
burgebjburgebj

skill-review-response

Evaluates code review feedback to verify claims before deciding whether to implement changes.

Community
Intermediate
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
duongbui234duongbui234

receiving-code-review

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

Community
Advanced