One-click install
npx skills add https://github.com/benjgrad/clawdbot --skill receiving-code-review-benjgrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/benjgrad/clawdbot/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/benjgrad/clawdbot --skill receiving-code-review-benjgrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you navigate code review feedback by ensuring technical rigor and verification before implementation, preventing performative agreement or blind execution of potentially flawed suggestions.

Core Features & Use Cases

  • Structured Response Pattern: Follows a clear process: Read, Understand, Verify, Evaluate, Respond, Implement.
  • Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
  • External Reviewer Scrutiny: Outlines a verification checklist for feedback from sources outside your immediate team.
  • YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary feature creep.
  • Use Case: When a reviewer suggests a change that seems technically unsound or unnecessary for the current project goals, this Skill guides you to ask clarifying questions, push back with technical reasoning, or verify its necessity against actual codebase usage.

Quick Start

When receiving code review feedback, verify its technical soundness against the codebase before implementing any suggestions.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I critically evaluate code review feedback before implementing changes?

Critically evaluating code review feedback involves verifying suggestions against codebase realities and project goals before implementation, prioritizing technical rigor over performative agreement to prevent blind execution of flawed recommendations.

What is the best way to handle unclear code review comments?

Handling unclear code review comments requires following structured steps to seek clarification, ensuring you understand the intent behind the feedback before proceeding with any code modifications.

How do I push back against technically unsound code review suggestions?

To push back against technically unsound code review suggestions, verify their necessity against actual codebase usage and respond with clear technical reasoning rather than performative agreement.

When should I apply the YAGNI principle to code review feedback?

Apply the YAGNI principle to code review feedback when a reviewer suggests changes that introduce unnecessary feature creep, evaluating whether the additions are actually needed for current project goals.

How do I verify feedback from external reviewers outside my team?

Verifying feedback from external reviewers involves applying a specific scrutiny checklist to evaluate technical soundness, ensuring their suggestions align with your immediate codebase context and project constraints.

What steps should I follow when receiving code review feedback?

When receiving code review feedback, follow a structured response pattern: Read, Understand, Verify, Evaluate, Respond, and Implement to ensure technical accuracy and necessity before changing code.