skills.rest
michalo1334
michalo1334COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated May 16, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill receiving-code-review-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill receiving-code-review-michalo1334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to broken code, wasted effort on unnecessary features, and missed clarification on unclear items. This Skill enforces a verify-before-implement discipline when responding to reviewers. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partners versus external reviewers, including pushback guidance and YAGNI checks for unused features. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing immediately, you grep the codebase for actual usage, verify platform compatibility, and either implement with a factual acknowledgment or push back with technical reasoning. ## 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 individual testing. Avoid performative phrases like "great point" and instead state the fix factually or push back with technical reasoning.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on any unclear items before implementing anything. Partial understanding leads to wrong implementations, especially when feedback items are related to each other.

When should I push back on a code review suggestion?▼

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 every suggestion from external reviewers?▼

No. External feedback is a suggestion to evaluate, not an order. Verify technical correctness for your codebase, check for regressions and platform compatibility, and confirm the reviewer understands the full context before implementing.

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

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→
Subaru-PFSSubaru-PFS
3

pr-description

Standardize pull request descriptions for HoloViz repositories using organizational templates.

Official
Basic
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
twjarviszyra-webtwjarviszyra-web
3

github-code-review

Review GitHub code changes for defects, security risks, and improvements.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced