skills.rest
raas-dev
raas-devOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Guide receiving code review feedback through verification and technical response.

19|4|Updated Dec 23, 2021
Search Tags:#code quality#code review#feedback#developer workflow#technical rigor#pushback
One-click install
npx skills add https://github.com/raas-dev/configent --skill receiving-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/raas-dev/configent/tree/main/etc/claude-code/skills/receiving-code-review
Command: npx skills add https://github.com/raas-dev/configent --skill receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you through receiving code review feedback with technical rigor, preventing performative agreement or blind implementation, and ensuring every suggestion is verified and technically sound for the codebase.

Core Features & Use Cases

  • Verify Before Implement: Mandates checking feedback against codebase reality before acting, preventing incorrect changes.
  • Clarification Protocol: Guides asking for clarification on unclear items before implementing anything, ensuring full understanding.
  • Reasoned Pushback: Provides guidance on when and how to technically push back on questionable suggestions, maintaining code quality.
  • Anti-Performative Responses: Forbids "You're absolutely right!" or "Thanks!" in favor of technical acknowledgment or action, fostering honest communication.
  • Use Case: When a reviewer suggests a change that seems incorrect or unclear, use this skill to systematically verify the suggestion, ask clarifying questions, or provide technical reasoning for not implementing it, ensuring only valid improvements are made.

Quick Start

WHEN receiving code review feedback:

1. READ: Complete feedback without reacting

2. UNDERSTAND: Restate requirement in own words (or ask)

3. VERIFY: Check against codebase reality

4. EVALUATE: Technically sound for THIS codebase?

5. RESPOND: Technical acknowledgment or reasoned pushback

6. IMPLEMENT: One item at a time, test each