skills.rest
thienty1207
thienty1207COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

1|Updated Sep 10, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill receiving-code-review-thienty1207
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill receiving-code-review-thienty1207

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 or adding a "proper" feature, verify against the actual codebase first, push back with technical reasoning if the suggestion breaks compatibility, and reply in GitHub comment threads correctly. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback before I implement any of the suggested 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 in your own words, verify it against the codebase, then implement one item at a time with individual testing. Avoid performative agreement like "great point" and skip straight to technical acknowledgment or action.

What should I do when code review feedback is unclear?▼

Stop and ask for clarification before implementing anything, even if you understand some items. Partial understanding leads to wrong implementation because feedback items are often related.

When is it appropriate to 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 code rather than being defensive.

How do I handle code review feedback from external reviewers?▼

Verify external suggestions against your codebase before implementing: check technical correctness, platform compatibility, and whether the reviewer understands full context. If you cannot verify something, state the limitation and ask for direction.

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

Reply within the comment thread using the GitHub API endpoint for comment replies (gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies), not as a top-level PR comment.

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

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

Community
Advanced
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
summarybotngsummarybotng
2

code-review-quality

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

Official
Advanced