skills.rest
ttnhan18062000
ttnhan18062000COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Feb 8, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill receiving-code-review-ttnhan18062000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/docs/archive/legacy_agents_skills_20260722/receiving-code-review
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill receiving-code-review-ttnhan18062000

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, and 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, verify build targets and backward compatibility requirements first, then push back with technical reasoning if the suggestion breaks existing functionality. ## Quick Start Apply the receiving-code-review skill to evaluate the reviewer 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 do I respond to code review feedback professionally?▼

Restate the technical requirement, verify it against the codebase, then implement one item at a time with individual testing. Avoid performative agreement like "great point" and instead state the fix or ask clarifying questions.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on all unclear items before implementing anything. Partial understanding leads to wrong implementation since feedback items are often related.

When should I push back on code review suggestions?▼

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 implement all external reviewer feedback immediately?▼

No. External feedback is a suggestion to evaluate, not an order. Verify technical correctness for your codebase, check for regressions, and confirm the reviewer understands the full context before implementing.

What order should I implement multi-item review feedback in?▼

Clarify unclear items first, then implement blocking issues like breaks and security fixes, followed by simple fixes like typos, then complex refactoring. Test each fix individually and verify no regressions.

Related Skills

Explore More Software Engineering Skills→
n8n-ion8n-io
199.9k

create-pr

Create GitHub pull requests with compliant type(scope): summary titles via CLI or API.

Official
Advanced
roycolumbia-coderoycolumbia-code

gsd-ship

Automates GitHub pull request creation, review triggering, and merge tracking.

Community
Intermediate
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
summarybotngsummarybotng
2

code-review-quality

Conduct context-driven code reviews focusing on quality, testability, and maintainability.

Official
Advanced