skills.rest
jordanhindo
jordanhindoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Verify pull request review feedback against the codebase before implementing changes.

4|1|Updated Jan 22, 2026
Search Tags:#code review#YAGNI#verification#pull requests#technical rigor#regression testing#clarifying questions
One-click install
npx skills add https://github.com/jordanhindo/Turtlez --skill receiving-code-review-jordanhindo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/jordanhindo/Turtlez/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/jordanhindo/Turtlez --skill receiving-code-review-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect or premature code changes by ensuring you understand, verify, and evaluate review feedback against the actual codebase.

Core Features & Use Cases

  • Verification-first implementation: Restates the requested change, checks it against real codebase behavior, and only then proceeds.
  • Clarity gating for unclear items: Stops and asks targeted questions when any part of the feedback is ambiguous.
  • Skeptical handling for external suggestions: Cross-checks technical correctness, regressions, compatibility, and scope (including YAGNI checks) before acting.

Example use case: A reviewer asks you to “remove legacy code” or “implement properly,” but you’re not sure the feature is used—this Skill directs you to verify usage in the codebase and either proceed or push back with technical reasoning.

Quick Start

Use this skill when you receive a pull request review comment and need to evaluate it technically, verify applicability to the codebase, and decide whether to ask questions, push back, or implement one validated 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 verify code review feedback before implementing pull request changes?▼

To verify code review feedback, restate the requested change, cross-check it against real codebase behavior for correctness, and evaluate potential regressions before proceeding with implementation. This ensures you only apply technically valid modifications.

What should I do when a pull request review comment is ambiguous or unclear?▼

When pull request review feedback is ambiguous, use clarity gating by stopping to ask targeted clarifying questions. This prevents incorrect modifications by ensuring you fully understand the requested scope before writing any code.

How do I push back on code review suggestions that violate YAGNI principles?▼

To push back on YAGNI violations, verify whether the suggested feature or change is actually used in the codebase. If it introduces unnecessary scope, respond with technical reasoning explaining why the implementation is premature.

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

Handle external suggestions skeptically by cross-checking technical correctness, compatibility constraints, and potential regressions. Implement validated changes incrementally, testing one item at a time to ensure codebase stability.

When should I ask clarifying questions during a code review instead of implementing directly?▼

Ask clarifying questions during a code review whenever any part of the feedback is technically questionable or its applicability to the codebase is uncertain, ensuring you confirm scope and correctness before making changes.

Related Skills

Explore More Software Engineering Skills→
PlazaCCPlazaCC
2

receiving-code-review

Verify code review feedback and plan implementation steps.

Official
Intermediate
EricOo0EricOo0
6

receiving-code-review

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

Community
Advanced
bnadlerjrbnadlerjr
5

receiving-code-review

Evaluate code-review feedback for technical correctness before implementation.

Community
Intermediate
dsivovdsivov

clean-code-practices

Enforce KISS, DRY, and YAGNI standards during software development tasks.

Community
Intermediate