skills.rest
ksolomon
ksolomonCOMMUNITY
Explore all skills by this author →
Website𝕏@KeithInWpgGitHub

receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

1|Updated Jul 6, 2015
Search Tags:#code review#feedback#pull request#YAGNI#github#verification#pushback
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill receiving-code-review-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/cache/claude-plugins-official/superpowers/6.1.1/skills/receiving-code-review
Command: npx skills add https://github.com/ksolomon/dotfiles --skill receiving-code-review-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing verification, clarification, and reasoned pushback before any code changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, including YAGNI checks for unused features. - Use Case: When a reviewer suggests removing legacy code, you verify build targets and backward compatibility requirements first, then push back with technical reasoning if the suggestion would break existing functionality. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request.

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 professionally?▼

Restate the technical requirement, verify it against the codebase, then implement one item at a time with testing. Avoid performative agreement like "great point" and instead state the fix or push back with technical reasoning when the suggestion is wrong.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on all unclear items before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related, so clarify everything first.

When should I push back on code review suggestions?▼

Push back when a suggestion breaks existing functionality, violates YAGNI for unused features, is technically incorrect for your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working tests or code.

Should I implement all external reviewer feedback automatically?▼

No, external feedback is a suggestion to evaluate, not an order. Check whether it is technically correct for your codebase, breaks existing functionality, and whether the reviewer understands the full context before implementing.

How do I reply to inline review comments on GitHub?▼

Reply within the comment thread using the GitHub API endpoint for pull request comment replies, not as a top-level PR comment. This keeps the discussion attached to the specific code line being reviewed.

Related Skills

Explore More Software Engineering Skills→
LAF-USLAF-US

gh-address-comments

Cluster GitHub PR feedback by file and apply traceable fixes.

Official
Intermediate
NJX-njxNJX-njx
55

prepare-pr

Rebase GitHub pull requests onto main, fix review issues, and run build and test gates.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
summarybotngsummarybotng
2

code-review-quality

Conduct context-driven code reviews focusing on quality, testability, and maintainability.

Official
Advanced