receiving-code-review

Restate code review feedback and verify against the repository before implementing changes.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill receiving-code-review-jayhjenkins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/jayhjenkins/Dev-Team-Full-SDLC/tree/main/vendor/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/jayhjenkins/Dev-Team-Full-SDLC --skill receiving-code-review-jayhjenkins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback can be unclear or emotionally charged. This skill enforces a structured verification before implementing changes to ensure technical correctness and alignment with repository reality.

Core Features & Use Cases

  • Read & Restate: Restate the reviewer’s requirement in your own words to confirm understanding.
  • Verify Against Codebase: Check feasibility against current code and tests, and identify gaps.
  • Reason & Respond: Provide technical rationale, raise clarifying questions, or push back with solid justification.
  • Incremental Implementation: Address feedback item by item, verifying each change with tests.

Quick Start

Paste a code-review comment into your AI prompt and follow the steps to read, understand, verify, and respond with a technically grounded plan before implementing changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How should I respond to unclear code review feedback on a pull request?

Respond to unclear code review feedback by first restating the reviewer's requirement to confirm understanding, then verifying feasibility against the current repository code and tests before providing technical rationale or pushing back with justification.

What is the best way to verify code review comments against an existing codebase?

The best way to verify code review comments is to read the feedback, restate the requirements in your own words, check the requested changes against current code and tests for gaps, and evaluate technical feasibility before implementing any fixes.

Can I push back on a code review comment with technical justification?

Yes, you can push back on a code review comment with technical justification after verifying the requested changes against the repository reality, identifying feasibility gaps, and formulating a technically grounded rationale or clarifying questions.

How do I implement code review feedback incrementally without breaking existing tests?

Implement code review feedback incrementally by addressing each item individually, verifying every change against existing tests and codebase constraints, and ensuring technical correctness through structured verification before pushing the final fixes.

What steps ensure technical correctness when addressing pull request review comments?

Steps ensuring technical correctness include reading and restating the review requirement, verifying against the codebase, evaluating feasibility, responding with technical rationale, and implementing changes item by item with continuous test verification.

Why do I need to restate requirements before fixing code review feedback?

Restating requirements before fixing code review feedback ensures you confirm understanding of the reviewer's intent, preventing emotionally charged or misinterpreted changes by enforcing a structured verification against repository reality before implementation.