skills.rest
LeonardoTan19
LeonardoTan19COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify and clarify code-review feedback before implementing incremental changes.

2|1|Updated May 1, 2026
Search Tags:#feedback#verification#clarification#code-review#pull-request#incremental-changes
One-click install
npx skills add https://github.com/LeonardoTan19/metaforge --skill receiving-code-review-leonardotan19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/LeonardoTan19/metaforge/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/LeonardoTan19/metaforge --skill receiving-code-review-leonardotan19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often surface unclear or conflicting feedback. This Skill provides a disciplined protocol to verify requirements before implementing changes, reducing blind edits and escalation risk.

Core Features & Use Cases

  • Clarify requirements: Restate feedback in your own words to ensure shared understanding.
  • Verify against reality: Check each item against the codebase, tests, and constraints before acting.
  • Incremental implementation: Apply changes one item at a time with traceable rationale and verification.
  • Handle unclear feedback: Pause, ask for clarification, and push back with technical reasoning when needed.
  • Guardrails for safety: Prioritize correctness, maintainability, and alignment with the design/plan.

Quick Start

Pause on feedback, restate the requirement in your own words, verify against the codebase, and implement changes one item at a time.

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 unclear code-review feedback on a pull request?▼

Handle unclear code-review feedback by pausing to restate the requirement in your own words, verifying it against the codebase, and asking for clarification before making any edits.

What is the best way to verify conflicting code-review requirements before implementing changes?▼

Verify conflicting code-review requirements by checking each item against the codebase, tests, and project constraints to evaluate correctness before pushing back with technical reasoning.

How do I implement code-review changes incrementally with traceable rationale?▼

Implement code-review changes incrementally by applying one item at a time, verifying each against the design plan, and documenting the rationale to maintain traceability and safety.

Does this code-review protocol work for any programming language or tech stack?▼

Yes, this code-review protocol applies across any programming language or tech stack, enforcing a six-step practice to handle edge cases and maintain correctness during pull-request cycles.

What steps should I follow to evaluate code-review comments before acting on them?▼

Evaluate code-review comments by following a six-step practice: read, understand, verify, evaluate, respond, and implement, ensuring you prioritize maintainability and design alignment.

When should I push back on code-review feedback instead of immediately making changes?▼

Push back on code-review feedback when items fail verification against the codebase or tests, using technical reasoning to address unclear requirements and reduce blind edits or escalation risk.

Related Skills

Explore More Software Engineering Skills→
swissonidswissonid

receiving-code-review

Automate code review feedback handling with read-understand-verify steps.

Community
Advanced
connectwithprakashconnectwithprakash

GitHub Issue Fixer

Fix GitHub issues end-to-end from exploration to linked pull request creation.

Community
Advanced
yikartyikart
24.9k

sync-service-docs

Generate and incrementally update API documentation from OpenAPI specifications and source code changes.

Official
Intermediate
MatrixFounderMatrixFounder
4

light-mode

Define criteria for trivial code fixes and enforce safety rules.

Community
Basic