receiving-code-review

Evaluate code review feedback against codebase logic and architectural constraints.

Updated Nov 18, 2025

Search Tags:#code review #pull request #refactoring #verification #technical rigor #yagni

Ready to run

npx skills add https://github.com/conejoRojo/DeployTime --skill receiving-code-review-conejorojo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/conejoRojo/DeployTime/tree/main/_agent/skills/receiving-code-review
Command: npx skills add https://github.com/conejoRojo/DeployTime --skill receiving-code-review-conejorojo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation of feedback, ensuring that code changes remain technically sound and aligned with project requirements.

Core Features & Use Cases

Verification-First Workflow: Mandates checking feedback against codebase reality before implementation.
Technical Pushback: Provides a framework for questioning or rejecting suggestions that violate YAGNI, break functionality, or lack context.
Use Case: When an external reviewer suggests a complex refactor that is not currently used in the codebase, use this skill to verify usage and push back with technical reasoning instead of blindly implementing.

Quick Start

Invoke the receiving-code-review skill to analyze the latest pull request feedback and generate a verification plan before making any code 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 evaluate code review feedback before making changes?▼

Evaluating code review feedback requires verifying suggestions against existing codebase logic and architectural constraints before implementation. This prevents performative agreement by mandating a verification-first workflow that checks technical accuracy and project alignment.

How do I push back on pull request feedback that suggests unnecessary refactoring?▼

Pushing back on pull request feedback involves applying YAGNI principles to question suggestions lacking context or violating project requirements. You can reject unnecessary refactoring by providing technical reasoning grounded in actual codebase usage rather than blindly implementing changes.

What is the best way to verify external code review suggestions against a codebase?▼

The best way to verify external code review suggestions is generating a verification plan that cross-references feedback with current codebase reality. This ensures implementations are validated against existing logic and architectural constraints before any modifications begin.

How do I prevent blind implementation of technical feedback during collaborative development?▼

Preventing blind implementation of technical feedback requires a verification-first workflow that evaluates external suggestions for technical accuracy. This framework ensures all pull request changes maintain technical rigor and remain aligned with actual project requirements.

When should I reject code review suggestions during pull request management?▼

You should reject code review suggestions when feedback violates YAGNI principles, breaks existing functionality, or lacks necessary codebase context. Technical pushback is justified when recommendations fail verification against current architectural constraints.

Can I use a verification workflow to manage complex refactoring suggestions in code reviews?▼

A verification workflow effectively manages complex refactoring suggestions by checking whether proposed changes align with actual codebase usage. This approach validates technical accuracy and ensures implementations match existing logic before proceeding with modifications.