skills.rest
rinbarpen
rinbarpenCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Jan 12, 2025
Search Tags:#code review#feedback#collaboration#pull request#github#verification#yagni
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill receiving-code-review-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/receiving-code-review
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill receiving-code-review-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind or performative implementation of code review feedback by enforcing a verify-first workflow that protects the codebase from incorrect or context-lacking suggestions. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with testing. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, with explicit pushback guidance. - YAGNI and Unclear-Feedback Checks: Greps the codebase for actual usage before adding features and stops to clarify ambiguous items before implementing. - Use Case: When a reviewer on a GitHub pull request suggests removing legacy code or adding a metrics endpoint, verify the suggestion against the codebase, push back with technical reasoning if wrong, and reply in the correct comment thread. ## Quick Start Apply 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 should I respond to code review feedback before implementing it?▼

Read the full feedback, restate the requirement, verify it against the codebase, then implement one item at a time with testing. Avoid performative agreement like "great point" and never implement before verification.

How do I handle unclear code review comments?▼

Stop and ask for clarification on the unclear items before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related.

When should I push back on a reviewer's suggestion?▼

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

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.

What is the YAGNI check for reviewer-suggested features?▼

Grep the codebase for actual usage of the suggested feature or endpoint. If nothing calls it, propose removing it instead of implementing it, since unused features add maintenance cost.

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

Provide structured, actionable feedback for code reviews and mentoring sessions.

Community
Advanced
p-o-ke-naep-o-ke-nae

github-flow

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

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