receiving-code-review

Verify code-review feedback against the codebase and tests before implementing changes.

29|1|Updated Jul 18, 2015

Search Tags:#verification #quality-assurance #code-review #software-engineering #pull-request #feedback-management

Ready to run

npx skills add https://github.com/joshmanders/dotfiles --skill receiving-code-review-joshmanders

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/joshmanders/dotfiles/tree/main/claude/skills/receiving-code-review
Command: npx skills add https://github.com/joshmanders/dotfiles --skill receiving-code-review-joshmanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code review feedback is easy to misinterpret or implement incorrectly. This Skill enforces a rigorous, technically-grounded approach to verify requirements against the codebase before making changes.

Core Features & Use Cases

Restate and confirm feedback requirements to avoid misinterpretation.
Verify feedback against the codebase and tests to determine what actually needs changing.
Plan, implement, and test changes one at a time to prevent regressions and ensure correctness.

Quick Start

Describe the feedback, verify requirements against the codebase, and plan one testable change at a time.

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 restating requirements, cross-referencing the codebase and tests to confirm technical correctness, and planning one testable change at a time to prevent blind compliance and regressions.

What is the best way to handle ambiguous pull request feedback?▼

Handling ambiguous pull request feedback requires cross-referencing the codebase and tests to validate what must be changed, ensuring you document justifications rather than blindly implementing questionable suggestions.

Why does implementing code review comments without verification cause regressions?▼

Implementing code review comments without verification causes regressions because feedback is easily misinterpreted; blindly applying changes skips validating against the repository and testing each modification individually.

Can I use this code review verification process for any software project pull request?▼

Yes, you can apply this code review verification process to typical pull requests across software projects, ensuring requirements are restated, validated against the repository, and tested individually before merging.

When do I need to document justifications for code review changes?▼

You need to document justifications for code review changes when feedback is questionable or ambiguous, enforcing a rigorous approach to confirm technical correctness and prevent blind compliance with incorrect suggestions.