Verified:GitHub

receiving-code-review

Verifies reviewer feedback against code before applying fixes.

Updated Jun 18, 2026

Search Tags:#software engineering #code review #pull request #review workflow #fix validation #feedback verification

One-click install

npx skills add https://github.com/hugefiver/ocmm --skill receiving-code-review-hugefiver

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hugefiver/ocmm/tree/main/dsmm/skills/receiving-code-review
Command: npx skills add https://github.com/hugefiver/ocmm --skill receiving-code-review-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often arrives as unverified claims, and blindly applying every suggestion can introduce regressions or out-of-scope changes. This Skill enforces a verify-first workflow so only confirmed issues get fixed. ## Core Features & Use Cases - Claim Verification: Reproduce or inspect each reviewer finding in the current code before changing anything. - Scoped Fixes: Fix only confirmed issues within the requested scope, avoiding scope creep. - Evidence Re-run: Re-run the tests or evidence that prove each fix works. - Use Case: A reviewer flags three potential bugs in your pull request. Use this Skill to check each claim against the actual code, fix the two that are real, re-run the failing tests, and re-submit for review. ## Quick Start Use the receiving-code-review skill to verify and address the reviewer feedback 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 handle code review feedback on a pull request?▼

Treat each review comment as a claim to verify, not a command. Reproduce or inspect the finding in the current code, fix only confirmed issues within the requested scope, then re-run the evidence proving the fix before re-submitting.

Should I apply every suggestion from a code reviewer?▼

No. Reviewer feedback can contain incorrect or outdated claims. Verify each finding against the actual code first, and only fix issues you can confirm are real and within the requested scope.

What should I do after fixing code review findings?▼

Re-run the evidence that proves the fix, such as the failing test or reproduction steps. Then re-submit the change for review when the workflow requires it.

When should I not act on reviewer feedback immediately?▼

Do not act when the finding cannot be reproduced or inspected in the current code, or when the requested change falls outside the review scope. Confirm the issue first to avoid unnecessary or harmful edits.