skills.rest
zMynxx
zMynxxCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Jun 5, 2026
Search Tags:#testing#code review#feedback#pull request#github#verification#pushback
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill receiving-code-review-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/agent/skills/receiving-code-review
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill receiving-code-review-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often triggers performative agreement or blind implementation, leading to wrong fixes, broken functionality, and unverified changes. This Skill enforces a verify-first workflow so feedback is evaluated against the actual codebase before any code changes. ## 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 criteria and YAGNI checks. - Use Case: When a reviewer on a pull request suggests six changes and two are unclear, the Skill instructs you to clarify items 4 and 5 before implementing anything, then verify each suggestion against the codebase and test each fix individually. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before making 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 full feedback, restate the requirement in your own words, verify it against the actual codebase, then respond with technical 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 before implementing anything. If you understand items 1, 2, 3, and 6 but not 4 and 5, state which items are clear and request clarification on the rest, since partial understanding leads to wrong implementation.

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.

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

Yes. Feedback from your trusted human partner can be implemented after understanding, while external reviewer suggestions require verification against the codebase first. If external feedback conflicts with prior decisions, discuss with your partner before proceeding.

How do I reply to inline review comments on GitHub pull requests?▼

Reply within the comment thread using the GitHub API replies endpoint for that specific comment, not as a top-level PR comment. This keeps the discussion attached to the relevant code line.

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

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

Community
Advanced
lonestar62lonestar62

prepare-pr

Rebase GitHub pull requests onto main and run build, check, and test gates.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
srbhrsrbhr
28.1k

receiving-code-review

Guide engineers through code-review feedback using a six-step response pattern.

Community
Basic