receiving-code-review

Verify code-review feedback against the codebase before implementing fixes.

Updated Mar 17, 2017
One-click install
npx skills add https://github.com/dfmonaco/dotfiles --skill receiving-code-review-dfmonaco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/dfmonaco/dotfiles/tree/main/archive/agents-skills/receiving-code-review
Command: npx skills add https://github.com/dfmonaco/dotfiles --skill receiving-code-review-dfmonaco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures we verify and interpret incoming code-review feedback for technical accuracy before applying changes, reducing misinterpretations and blind agreement.

Core Features & Use Cases

  • Verifies each review item against the codebase and project requirements to determine validity and potential impact.
  • Promotes clear, justified feedback with a structured, risk-aware response when suggestions are incorrect, unclear, or out of scope.
  • Maintains rigorous standards by preventing blind agreement and ensuring changes align with the intended design and constraints.

Quick Start

Review incoming feedback by verifying the technical requirements before making changes.

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 applying changes?

Verify code review feedback by checking each comment against the actual codebase and project requirements to determine correctness, scope, and risk before proposing or implementing fixes.

What should I do when code review suggestions are incorrect or out of scope?

When code review suggestions are incorrect or out of scope, you should push back with clear justification and a structured, risk-aware response instead of blindly agreeing to the changes.

How can I assess the risk of code review comments?

Assess the risk of code review comments by applying verification against the actual codebase and project requirements to determine their validity and potential impact on the intended design.

Why do I need to interpret code review feedback before acting on it?

Interpreting code review feedback before acting reduces misinterpretations and blind agreement, ensuring that any changes align with the intended design constraints and maintain rigorous quality standards.

Can I push back on unclear code review comments?

Yes, you can push back on unclear code review comments by providing a clear, justified response that highlights the ambiguity and ensures changes only happen after confirming correctness.