receiving-code-review

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

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Shresth-sh/resume-matcher-ai-project --skill receiving-code-review-shresth-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Shresth-sh/resume-matcher-ai-project/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/Shresth-sh/resume-matcher-ai-project --skill receiving-code-review-shresth-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback often contains ambiguity; this skill focuses on receiving feedback with technical rigor and verification before implementing suggestions.

Core Features & Use Cases

  • Read and restate requirements to ensure clarity
  • Verify feedback against the codebase before making changes
  • Provide technical acknowledgment or reasoned pushback, then implement items one by one
  • Improve collaboration and reduce misinterpretation in PR reviews

Quick Start

Restate the feedback, verify it against the codebase, and outline a safe, testable implementation plan item by item.

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 unclear code-review feedback on a pull request?

Handle unclear code-review feedback by restating the requirements to ensure clarity, verifying the suggestion against the codebase, and outlining a safe, testable implementation plan item by item.

What is the best way to verify technical feedback before implementing changes?

Verify technical feedback by checking the suggestion against the codebase, evaluating its technical validity, and providing a reasoned pushback or acknowledgment before implementing the fix.

How do I respond to questionable code-review suggestions safely?

Respond to questionable suggestions by reading, understanding, verifying, and evaluating the feedback first, then providing a reasoned pushback or acknowledgment before implementing one item at a time.

Can I address code-review items one by one instead of all at once?

Yes, you can address code-review items one by one by following a six-step process: read, understand, verify, evaluate, respond, and implement each item individually to improve collaboration and reduce misinterpretation.

When do I need to apply technical rigor to code-review feedback?

Apply technical rigor when code-review feedback contains ambiguity or is technically questionable, requiring verification before implementation across code reviews, pull requests, and collaborative fixes.