skills.rest
lowmason
lowmasonCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback with verification against codebase requirements.

Updated Jun 20, 2026
Search Tags:#code-quality#quality-assurance#code-review#pull-request#development-workflow#technical-rigor#feedback-verification
One-click install
npx skills add https://github.com/lowmason/agent-skills --skill receiving-code-review-lowmason
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/lowmason/agent-skills/tree/main/receiving-code-review
Command: npx skills add https://github.com/lowmason/agent-skills --skill receiving-code-review-lowmason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams handle code review feedback with technical rigor before implementing changes, reducing blind agreement and rework.

Core Features & Use Cases

  • Structured feedback handling: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT steps to ensure changes align with requirements and context.
  • Clarity when unclear: If any item is unclear, STOP and ask for clarification before proceeding.
  • Source-specific guidance: Guidelines for interactions with human partners vs external reviewers, including pushing back with technical reasoning when needed.
  • Implementation discipline: Prioritizes blocking issues, then simple fixes, then complex changes, with one change at a time and regression checks.

Quick Start

Ask clarifying questions about ambiguous feedback and verify requirements against the codebase before starting any 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 evaluate code review feedback before implementing changes?▼

Handling pull request feedback involves reading, understanding, verifying requirements, evaluating, responding, and implementing. If any feedback is unclear, stop and ask for clarification before proceeding with any code changes.

What is the best way to handle ambiguous code review comments?▼

The best way to handle ambiguous code review comments is to stop immediately and ask for clarification. Verify the feedback against the codebase reality before responding or starting any implementation to prevent unsafe or unnecessary changes.

How do I push back on code review feedback with technical reasoning?▼

Pushing back on code review feedback with technical reasoning involves verifying the suggestion against the codebase, evaluating its impact, and responding with clear technical justification. This applies to both internal human partners and external reviewers.

In what order should I implement code review fixes?▼

Implement code review fixes by prioritizing blocking issues first, then simple fixes, and finally complex changes. Execute one change at a time and run regression checks to ensure code quality and development workflow stability.

Can I apply code review feedback workflows to data pipelines and library maintenance?▼

Yes, you can apply code review feedback workflows to data pipelines and library maintenance. The structured feedback handling process works across software development workflows, accommodating feedback from both internal and external reviewers.

Related Skills

Explore More Software Engineering Skills→
wangx7wangx7

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
zerielribeirozerielribeiro

lint-and-validate

Run ESLint, Ruff, and MyPy to lint and statically analyze JavaScript and Python code.

Community
Intermediate
hospitaljobsinhospitaljobsin
7

code-review-excellence

Structure code reviews with checklists and feedback templates.

Official
Intermediate