skills.rest
victorqnguyen
victorqnguyenCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verifies codebase impact of feedback before implementing changes.

Updated Aug 23, 2026
Search Tags:#testing#debugging#verification#code-review#guardrails#pull-request#technical-judgement
One-click install
npx skills add https://github.com/victorqnguyen/victors-architecture --skill receiving-code-review-victorqnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/victorqnguyen/victors-architecture/tree/main/packages/core/skills/receiving-code-review
Command: npx skills add https://github.com/victorqnguyen/victors-architecture --skill receiving-code-review-victorqnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers verify and interpret code review feedback before implementing any changes, ensuring technical correctness and preventing performative agreement or rushed fixes.

Core Features & Use Cases

  • Feedback interpretation: restate requirements in your own words to confirm understanding.
  • Technical verification: check against the codebase to assess feasibility and impact.
  • Clarification requests: ask precise questions when requirements are unclear.
  • Incremental changes and testing: implement changes one at a time with tests to guard against regressions.
  • Reasoned pushback: provide technical justification when a suggested change is incorrect or unnecessary.

Quick Start

Review the feedback thoroughly, restate the requirement, verify it against the codebase, and propose a technically justified plan before implementing.

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 restating the requirement, checking it against the codebase for feasibility and impact, and proposing a technically justified plan before implementation.

What is the best way to handle incorrect pull request feedback?▼

Handle incorrect pull request feedback by pushing back with technical justification, ensuring changes are tested incrementally with guardrails against regressions to prove the flaw.

How do I prevent performative agreement when responding to code review comments?▼

Prevent performative agreement by applying rigorous technical reasoning, asking precise clarifying questions when scope is unclear, and confirming your understanding of the feedback.

When should I ask clarifying questions during a code review?▼

Ask clarifying questions during a code review when requirements are unclear, restate the feedback in your own words to confirm understanding, and check the codebase impact before proceeding.

How do I implement code review changes without introducing regressions?▼

Implement code review changes without regressions by applying them one at a time, using incremental testing, and maintaining technical guardrails throughout the verification process.

Does this approach to code review verification work for debugging and testing workflows?▼

This approach works for debugging and testing workflows by integrating technical judgement, incremental verification, and regression guardrails directly into your pull request implementation process.

Related Skills

Explore More Software Engineering Skills→
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
bnadlerjrbnadlerjr
5

receiving-code-review

Evaluate code-review feedback for technical correctness before implementation.

Community
Intermediate
ys0714ys0714

qa-tester

Run Vitest and TypeScript test suites with failure diagnosis and repair attempts.

Community
Advanced
keshavraj936keshavraj936

lint-and-validate

Lint and statically analyze Node.js and Python code modifications.

Community
Intermediate