receiving-code-review

Process code review feedback with technical verification before implementation.

Updated Oct 25, 2023
One-click install
npx skills add https://github.com/Lordkaito/LKPortfolio --skill receiving-code-review-lordkaito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Lordkaito/LKPortfolio/tree/main/.github/skills/receiving-code-review
Command: npx skills add https://github.com/Lordkaito/LKPortfolio --skill receiving-code-review-lordkaito

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 acceptance of suggestions.

Core Features & Use Cases

  • Structured Response Pattern: Follows a clear process of reading, understanding, verifying, evaluating, responding, and implementing feedback.
  • Handling Ambiguity: Provides clear steps for asking clarification on unclear feedback.
  • External Reviewer Scrutiny: Outlines a rigorous checklist for evaluating feedback from external sources, prioritizing technical correctness and codebase integrity.
  • Use Case: When a reviewer suggests a change, you first verify its technical validity and impact on the existing codebase before agreeing or implementing, ensuring quality and preventing regressions.

Quick Start

When receiving code review feedback, first read and understand the feedback completely before verifying its technical soundness against the codebase.

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?

Verify code review feedback by reading it completely, understanding the intent, and checking its technical soundness against the existing codebase before implementation. This structured process ensures technical rigor and prevents performative agreement or blind acceptance of suggestions.

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

Handle unclear code review suggestions by following a structured protocol that provides clear steps for asking for clarification. This ensures you fully understand the feedback before evaluating its technical validity or attempting any implementation.

How do I push back on code review comments with technical reasoning?

Push back on code review comments by prioritizing technical correctness and codebase integrity over performative agreement. Evaluate the feedback against the codebase, enforce YAGNI principles, and respond with direct, factual acknowledgments instead of gratitude expressions.

How do I evaluate code review feedback from external reviewers?

Evaluate external code review feedback using a rigorous checklist that prioritizes technical correctness and codebase integrity. This scrutiny prevents regressions by ensuring suggested changes are technically valid and do not negatively impact the existing system.

When should I prioritize code review feedback implementation order?

Prioritize code review feedback implementation order after verifying the technical validity and impact of each suggestion. This ensures quality and prevents regressions by addressing changes based on technical reasoning rather than blind acceptance.

Can I use a structured protocol for receiving code review feedback in software development?

Yes, you can use a structured protocol for receiving code review feedback that follows a clear process of reading, understanding, verifying, evaluating, responding, and implementing. This enforces YAGNI principles and ensures technical rigor during software development.