skills.rest
mst-software-vn
mst-software-vnOFFICIAL
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

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

1|Updated Mar 2, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill receiving-code-review-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill receiving-code-review-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing verification, clarification, and reasoned pushback before any code 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: Applies different trust levels for feedback from your human partner versus external reviewers, including YAGNI checks for unused features. - Use Case: When a reviewer suggests removing legacy code or adding a feature, verify it against the actual codebase first, push back with technical reasoning if wrong, and implement only after clarification. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback 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 before implementing it?▼

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

How do I handle unclear items in multi-item code review feedback?▼

Stop and ask for clarification on all unclear items before implementing anything. Partial understanding leads to wrong implementation because items may be related, so clarify everything 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 the stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests.

Should external reviewer feedback be treated differently from my team lead's feedback?▼

Yes. Feedback from your human partner is trusted and implemented after understanding, while external feedback requires skepticism: verify correctness for this codebase, check for regressions, and confirm the reviewer understands full context.

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 comment ID, not as a top-level PR comment. This keeps the discussion attached to the specific code line being reviewed.

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
cpa03cpa03

code-review-checklist

Generate structured code-review checklists for pull requests, diffs, and commits.

Community
Basic
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced