skills.rest
jetteim
jetteimCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Process code-review feedback by extracting intent and verifying changes against the codebase.

Updated Apr 11, 2026
Search Tags:#implementation#clarification#pushback#code-review#pull-request#technical-verification
One-click install
npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill receiving-code-review-jetteim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/jetteim/platform-workstation-bootstrap/tree/main/agents/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill receiving-code-review-jetteim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams handle code review feedback by emphasizing verification, avoiding performative agreement, and ensuring changes are grounded in technical reasoning.

Core Features & Use Cases

  • Structured workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
  • Clarification-first approach: If any item is unclear, STOP and request clarification before proceeding.
  • Source-specific handling: Apply guidelines for external reviewers and your human partner to maintain technical rigor.
  • Pushback with reasoning: When feedback risks correctness or scope, push back with technical justification.
  • Incremental changes: Implement changes one item at a time and verify each change independently.

Quick Start

When you receive code review feedback, follow the structured response pattern and implement items one at a time after clarifying ambiguities.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback without just making every requested change?▼

Process code review feedback by extracting reviewer intent, verifying suggestions against the codebase, and drafting technically grounded responses. This approach enables justified pushback and clarifications rather than performative agreement.

What is the best way to handle unclear code review comments on a pull request?▼

Handle unclear code review comments by stopping immediately to request clarification before proceeding. This clarification-first approach prevents implementing incorrect fixes and ensures you understand the reviewer's actual intent.

How do I implement code review changes without introducing regressions?▼

Implement code review changes incrementally, processing one item at a time and verifying each change independently against the codebase. This procedural workflow enforces guardrails to verify changes before applying fixes, reducing regressions.

When should I push back on pull request feedback?▼

Push back on pull request feedback when suggestions risk code correctness or scope. Provide technical justification grounded in codebase verification rather than accepting feedback blindly, ensuring changes maintain technical rigor.

Does this code review response workflow work across different programming languages?▼

Yes, this code review response workflow applies to pull-request workflows across all programming languages. It focuses on procedurally processing feedback through understanding, verification, and evaluation stages regardless of language.

Related Skills

Explore More Software Engineering Skills→
yves-syves-s
24

receiving-code-review

Verify code review feedback against codebase context before implementing fixes.

Community
Intermediate
vp-kvp-k
12

flutter-review-receive

Evaluate Flutter code review feedback against the codebase and implement changes incrementally.

Community
Advanced
EotelEotel

refactor-clean

Identify and remove dead code with test verification and rollback.

Community
Intermediate
89jobrien89jobrien

review-pr

Read pr_diff.txt and pr_description.txt to generate review.json.

Community
Intermediate