skills.rest
arthrod
arthrodCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Standardize code review feedback reception through technical verification and reasoned discourse.

Updated Jul 18, 2026
Search Tags:#workflow#testing#code review#pull request#refactoring#technical rigor
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill receiving-code-review-arthrod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/arthrod/conejo-skills --skill receiving-code-review-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents performative agreement and blind implementation of code review feedback, ensuring that all changes are technically verified and aligned with the codebase's architectural standards.

Core Features & Use Cases

  • Technical Verification: Mandates a strict process of reading, understanding, and verifying feedback against the codebase before implementation.
  • Strategic Pushback: Provides a framework for challenging technically questionable or context-blind suggestions using objective reasoning.
  • Workflow Optimization: Enforces a one-item-at-a-time implementation and testing cycle to prevent regressions and ensure high-quality PR merges.

Quick Start

Use the receiving-code-review skill to evaluate the latest batch of pull request comments and determine which items require clarification versus immediate 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 handle code review feedback without just blindly implementing changes?▼

Code review feedback requires technical verification before implementation. You must read, understand, and verify suggestions against existing architectural doctrines, using reasoned discourse to push back on context-blind comments rather than performative agreement.

What is the best way to push back on technically questionable pull request comments?▼

Pushing back on pull request comments requires strategic, objective reasoning. Evaluate the suggestion's technical rigor against the codebase, then challenge context-blind feedback using non-performative communication to maintain architectural standards.

How do I implement multiple code review changes without causing regressions?▼

Implementing code review changes safely requires a one-item-at-a-time workflow. Process each suggestion sequentially through systematic testing to prevent regressions and ensure high-quality pull request merges.

When should I challenge code review feedback instead of applying it directly?▼

You should challenge code review feedback when suggestions conflict with existing architectural doctrines. Apply strict technical verification to determine if comments are context-blind, requiring reasoned discourse instead of blind implementation.

Does this code review workflow require a specific testing framework?▼

No specific testing framework is required, but the workflow mandates systematic testing of all proposed changes. You must verify each modification one item at a time to prevent regressions before merging the pull request.

What does non-performative communication mean when receiving pull request feedback?▼

Non-performative communication means avoiding agreement for appearances. It enforces technical rigor by requiring objective reasoning and strict verification of code review feedback against the codebase before any implementation actions.

Related Skills

Explore More Software Engineering Skills→
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
zli5460zli5460
2

test-driven-development

Guide developers through strict test-driven development cycles with failing tests first.

Community
Advanced
dogekikidogekiki

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate
tonombtonomb

setup-pre-commit

Configure Git pre-commit hooks with Husky and lint-staged.

Community
Intermediate