receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: miles990

Restate code-review feedback, verify against the codebase, and implement incremental tested changes.

Updated Jan 7, 2026

Search Tags:#testing #clarification #quality-assurance #code-review #pull-requests #technical-verification

Ready to run

npx skills add https://github.com/miles990/claude-starter-kit --skill receiving-code-review-miles990

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback is often unclear or technically questionable. This Skill provides a structured approach to interpret feedback, verify requirements, and plan safe, incremental changes.

Core Features & Use Cases

Clarification-first: Restate requirements to ensure alignment before acting.
Technical verification: Check proposed changes against the codebase, tests, and constraints.
Incremental implementation: Apply one change at a time with targeted tests to avoid regressions.
Pushback when needed: Provide reasoned, technical responses if a suggestion is incorrect or risky.

Quick Start

Upon receiving code-review feedback, read thoroughly, restate requirements, verify against the repository, decide if the suggestion is valid, and implement changes one at a time with tests.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I handle code-review feedback when the requirements are unclear?▼

Handle unclear code-review feedback by restating the request to ensure alignment before acting. Verify the suggestion against the codebase and constraints, then propose safe, incremental changes with tests.

What is the best way to respond to technically questionable pull-request suggestions?▼

Respond to questionable pull-request suggestions with reasoned technical pushback. Verify the proposed changes against existing tests and repository constraints, and provide clear, technical explanations if a suggestion is risky.

How do I implement code-review changes without causing regressions?▼

Implement code-review changes without regressions by applying one change at a time. Follow an incremental implementation approach with targeted tests before merging to ensure codebase stability.

Do I need to write tests before merging code-review feedback changes?▼

Yes, you need to write tests before merging code-review feedback changes. This skill enforces disciplined reasoning and step-by-step implementation with targeted tests to verify safety and prevent regressions.

When should I pushback on code-review feedback?▼

Pushback on code-review feedback when a suggestion is technically incorrect or risky. Provide a reasoned, technical response after verifying the proposed changes against the codebase and project constraints.

How does technical verification work for code-review feedback?▼

Technical verification for code-review feedback works by checking proposed changes against the codebase, existing tests, and project constraints. This ensures requirements are technically sound before incremental implementation.