skills.rest
gyc-12
gyc-12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

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

Updated Jun 9, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill receiving-code-review-gyc-12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/gyc-12/Archipelago/tree/main/modules/collaboration-runtime/src-tauri/experts/skills/receiving-code-review
Command: npx skills add https://github.com/gyc-12/Archipelago --skill receiving-code-review-gyc-12

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: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skeptical verification against the codebase. - YAGNI and Pushback Checks: Detects unused features before implementing "proper" solutions and provides technical reasoning when reviewer suggestions are wrong. - Use Case: When a reviewer on a GitHub pull request suggests removing legacy code, verify build targets and backward compatibility first, then either fix, push back with reasoning, or ask clarifying questions. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before implementing any 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 code review feedback before implementing it?▼

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, evaluate whether it is technically sound, then respond with acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

How do I handle unclear code review comments?▼

Stop and ask for clarification on unclear items before implementing anything. Partial understanding leads to wrong implementation because feedback items are often related, so clarify all items first rather than implementing only the ones you understand.

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 rather than being defensive.

Should I treat external reviewer feedback differently from my team lead's feedback?▼

Yes. Feedback from your human partner is trusted and can be implemented after understanding, while external reviewer suggestions require verification against the codebase, platform compatibility, and existing functionality before implementation.

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 rather than posting 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
I194I194
9

generate

Generate atomic commits with npm run verify for each feature or fix.

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