receiving-code-review

Verifies code-review feedback against the codebase before implementing incremental fixes.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/erenisiklar/Pusula --skill receiving-code-review-erenisiklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/erenisiklar/Pusula/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/erenisiklar/Pusula --skill receiving-code-review-erenisiklar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback can be unclear or technically questionable. This skill provides a disciplined, verifiable approach to interpret feedback, verify it against the codebase, and apply changes incrementally to ensure correctness.

Core Features & Use Cases

  • Structured response pattern: Read, understand, verify, evaluate, respond, and implement in a controlled sequence to prevent rash changes.
  • Clarification when unclear: If any item is ambiguous, stop and request clarification before proceeding.
  • Source-specific handling: Differentiate between trusted human partners and external reviewers, with appropriate pushback when scope is unclear.
  • YAGNI and validation checks: Assess whether suggested changes are actually needed and verify their impact before applying.
  • Implementation discipline: Prioritize blocking issues, then simple fixes, then complex refactors; test each change individually to avoid regressions.
  • Communication style: Provide technical acknowledgment or reasoned pushback without performative agreement.

Quick Start

When you receive code-review feedback, read it carefully, clarify unclear items, verify against the codebase, and implement changes one item at a time after validation.

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?

To verify code review feedback, evaluate suggestions against the codebase, check YAGNI principles, and validate impact before applying fixes incrementally to prevent regressions.

What is the best way to handle unclear code review comments on a pull request?

Handling unclear code review comments requires stopping implementation and requesting clarification before proceeding, ensuring ambiguous feedback is resolved to maintain technical rigor.

How do I push back on technical feedback from external reviewers?

Pushing back on technical feedback involves differentiating between trusted partners and external reviewers, then providing reasoned technical arguments without performative agreement when scope is unclear.

What is the correct order for implementing code review fixes?

The correct order for implementing code review fixes prioritizes blocking issues first, then simple fixes, and finally complex refactors, testing each change individually to avoid regressions.

When should I ask clarifying questions during a code review?

You should ask clarifying questions during a code review whenever any feedback item is ambiguous, stopping the implementation process until the technical requirements are fully validated and understood.