skills.rest
octanutri-clin
octanutri-clinCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind or performative responses to code review feedback by enforcing a verify-before-implement workflow, so suggestions are checked against the actual codebase before any changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback guidance and YAGNI checks. - Use Case: A reviewer asks to remove legacy code or add a metrics endpoint; the skill directs you to grep the codebase for actual usage, verify platform constraints, and push back with technical reasoning when the suggestion breaks compatibility. ## Quick Start Apply the receiving-code-review skill to evaluate the review comments on my 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 as a developer?▼

Read the full feedback, restate the requirement in your own words, verify it against the codebase, then implement one item at a time with testing. Avoid performative agreement like "great point" and use technical acknowledgment or reasoned pushback instead.

How do I handle unclear code review comments?▼

Stop and ask for clarification before implementing anything when any feedback item is unclear. Partial understanding leads to wrong implementations because items may be related, so clarify all ambiguous points first.

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 code or tests.

Should I implement every suggestion from external reviewers?▼

No. External feedback should be treated as suggestions to evaluate, not orders. Verify each suggestion against 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?▼

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 line of code 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
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
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