skills.rest
DecentralizedGeo
DecentralizedGeoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

1|Updated Jan 14, 2026
Search Tags:#verification#clarification#best-practices#pushback#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/DecentralizedGeo/stac-manager --skill receiving-code-review-decentralizedgeo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/DecentralizedGeo/stac-manager/tree/main/.github/skills/receiving-code-review
Command: npx skills add https://github.com/DecentralizedGeo/stac-manager --skill receiving-code-review-decentralizedgeo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often become emotionally driven or unclear; this skill promotes technical rigor and verification before implementing suggestions, ensuring changes are justified and correct.

Core Features & Use Cases

  • Core pattern: Read, Understand, Verify, Evaluate, Respond, Implement (one item at a time) to manage feedback deterministically.
  • Unclear feedback handling: If any item is unclear, stop and ask for clarification before proceeding.
  • Source-specific handling: Distinguishes trusted partners vs external reviewers; emphasizes verification and technical reasoning.
  • Guardrails: Encourages YAGNI, minimal changes, and avoids performative agreement.
  • Implementation order: Prioritize blocking issues, then simple fixes, then complex fixes; test each fix.

Quick Start

Observe feedback, restate requirements, 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 code review feedback without blindly implementing every suggestion?▼

Handling code review feedback requires structured verification before implementation. You should read, understand, verify against the codebase, and evaluate each suggestion to ensure changes are justified and technically correct, avoiding performative agreement.

What is the best way to respond to unclear feedback on a pull request?▼

The best way to respond to unclear pull request feedback is to stop and ask for clarification immediately. You must fully understand the technical requirement before proceeding with any implementation to avoid incorrect or unnecessary changes.

How do I prioritize fixes when addressing multiple comments in a code review?▼

Prioritize code review fixes by addressing blocking issues first, then simple fixes, and finally complex fixes. This deterministic implementation order ensures critical technical correctness is resolved before minor adjustments, with each fix tested individually.

When should I push back on code review suggestions from external reviewers?▼

You should push back on external code review suggestions when verification against the codebase shows they lack technical justification. Apply technical rigor to distinguish trusted partner feedback from external comments, ensuring changes follow YAGNI and minimal change principles.

Does this approach to code reviews work for cross-functional technical reviews?▼

Yes, this approach works for cross-functional technical reviews where technical correctness matters. It enforces risk assessment, clarification of unclear items, and unit-testable changes, ensuring feedback is processed deterministically regardless of the reviewer's domain.

Why do I need to verify code review suggestions against the codebase before implementing them?▼

Verifying code review suggestions against the codebase is necessary to prevent emotionally driven or incorrect changes. Technical verification ensures the proposed modifications are justified, maintain technical rigor, and result in unit-testable, minimal changes.

Related Skills

Explore More Software Engineering Skills→
orbtyapporbtyapp
1

receiving-code-review

Interpret and validate code-review feedback on pull requests before implementation.

Official
Basic
hugo-berendihugo-berendi
3

receiving-code-review

Guide engineers to verify code review feedback against the codebase before implementing changes.

Community
Basic
YomiamyYomiamy
16

receiving-code-review

Manage code review feedback with structured verification and questioning.

Community
Intermediate
cloudvoyantcloudvoyant

review

Validate code compliance with style guides and best practices.

Official
Advanced