skills.rest
DoraemonHugU
DoraemonHugUCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate GitHub PR review feedback with verification before implementation.

14|1|Updated May 24, 2026
Search Tags:#testing#github#implementation plan#yagni#code-review#technical validation#review rebuttal
One-click install
npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill receiving-code-review-doraemonhugu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/DoraemonHugU/oh-my-harness/tree/main/plugin/skills/receiving-code-review
Command: npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill receiving-code-review-doraemonhugu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from blindly accepting unclear or technically questionable code-review suggestions by enforcing verification first, then careful, test-backed responses and fixes.

Core Features & Use Cases

  • Evidence-first verification: read the full feedback, restate it, then validate against the actual codebase, tests, and documentation.
  • Technical evaluation and response: decide whether the suggestion is technically sound for the current repository context, and respond with confirmation or a technical rebuttal.
  • Controlled implementation with guardrails: implement one issue at a time, test each change, and avoid scope creep by following explicit P-level repair rules and YAGNI checks.

Quick Start

Use receiving-code-review when you receive GitHub code review comments and you need to validate, clarify, and then implement only what is technically correct and appropriately in-scope.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate technical feedback from a GitHub code review before implementing changes?▼

Validate code review feedback by restating the reviewer intent, running existing tests, and verifying against the codebase. This ensures suggestions are technically sound before you implement any changes.

What is the best way to respond to unclear or suspicious code review comments on a pull request?▼

Respond to unclear code review comments by creating minimal reproductions or tests to verify the issue. Use a structured review rebuttal template to confirm or technically dispute the suggestion.

How do I implement code review fixes without introducing scope creep?▼

Implement code review fixes item-by-item with regression safety. Apply YAGNI checks and explicit repair rules to each change, ensuring you only implement what is technically correct and in scope.

When should I provide a technical rebuttal to a code review suggestion?▼

Provide a technical rebuttal when code review suggestions are technically suspicious or invalid for your repository context. Verify the feedback against documentation and tests before replying with your rebuttal.

Do I need to write tests when processing GitHub PR review threads?▼

Yes, you need to run existing validations or create minimal reproductions and tests as needed. This evidence-first verification process ensures your implementation and review responses are technically backed.

Related Skills

Explore More Software Engineering Skills→
tech-leads-clubtech-leads-club
5.0k

gh-address-comments

Fetch GitHub pull request comments, reviews, and threads for the current branch.

Official
Intermediate
enigmaicon-engenigmaicon-eng
1

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate
JubaKitiashviliJubaKitiashvili
41

erne-orchestrate

Coordinate multi-agent plan-to-validate pipelines across React Native/Expo projects.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced