skills.rest
GaryOcean428
GaryOcean428COMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Verify code review feedback against the codebase before implementation.

Updated Feb 16, 2026
Search Tags:#code review#feedback#implementation#verification#technical rigor#pushback
One-click install
npx skills add https://github.com/GaryOcean428/vex-agent --skill receiving-code-review-garyocean428
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/GaryOcean428/vex-agent/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/GaryOcean428/vex-agent --skill receiving-code-review-garyocean428

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically verified and implemented correctly, preventing performative agreement and blind implementation of potentially flawed suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers the AI to critically assess code review suggestions against the codebase's reality.
  • Reasoned Pushback: Enables the AI to articulate technical objections or seek clarification when feedback is unclear or incorrect.
  • Use Case: When a reviewer suggests a change, the AI will first verify its technical soundness, check for regressions, and ensure it aligns with project goals before implementing, rather than blindly accepting.

Quick Start

Use the receiving-code-review skill to process feedback from your human partner on the latest commit.

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?▼

Code review feedback verification requires checking technical soundness against codebase reality, evaluating potential regressions, and ensuring alignment with project goals before proceeding with any implementation.

What is the best way to handle incorrect code review suggestions?▼

Handling incorrect code review suggestions involves articulating technical objections through reasoned pushback, requesting clarification when feedback is unclear, and avoiding performative agreement over technical rigor.

How do I prevent blind implementation of flawed code review comments?▼

Preventing blind implementation requires critically assessing reviewer suggestions, verifying their technical soundness against the actual codebase, and confirming they do not introduce regressions prior to execution.

Can I push back on external reviewer feedback if it lacks technical justification?▼

Pushing back on external reviewer feedback is necessary when suggestions lack technical justification, requiring you to evaluate the soundness of the request and respond with reasoned technical objections or clarifying questions.

When do I need technical rigor processing for code review feedback?▼

Technical rigor processing for code review feedback is needed when receiving suggestions from human partners or external reviewers to ensure accurate, justified implementation rather than performative agreement.

Why does performative agreement cause issues during code review implementation?▼

Performative agreement causes issues because it bypasses technical verification, leading to the blind implementation of potentially flawed suggestions that may introduce regressions or conflict with codebase reality.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
cskirocskiro
7

e2e-testing

Automate Playwright end-to-end test setup, generation, and regression detection.

Community
Advanced
abhishekdutta18abhishekdutta18

ai-regression-testing

Automate regression testing for AI-generated code with sandbox API tests.

Community
Intermediate
Disaster-TerminatorDisaster-Terminator
5

pr-review

Automate pull request reviews with AI bots and archive learnings.

Community
Advanced