Validate code-review feedback for technical correctness before implementation.
npx skills add https://github.com/hmps/skills --skill receiving-code-review-hmps
Please help me install this Agent Skill. Skill: receiving-code-review Source: https://github.com/hmps/skills/tree/main/receiving-code-review Command: npx skills add https://github.com/hmps/skills --skill receiving-code-review-hmps
This Skill transforms the often-tricky process of receiving code review feedback into a structured, technically rigorous workflow. It prevents blind implementation, ensures clarity, and empowers you to verify suggestions against codebase reality, saving time on rework and improving code quality.
Use the receiving-code-review skill to process the feedback on my latest pull request. I will start by reading all comments without reacting.
High-intent search queries and answers about installing and using this skill.
Validate code-review feedback by systematically reading, understanding, and verifying each suggestion against your codebase reality before implementation. This structured approach prevents blind changes, catches technically questionable feedback, and ensures clarity on intent across diverse codebases and languages.
Push back when feedback violates architectural principles, contradicts established patterns, or lacks technical justification. Use systematic verification to articulate your reasoning with codebase evidence, enabling productive discussion rather than implementing potentially harmful changes.
Follow a six-step workflow: read all feedback without reacting, understand each point's intent, verify suggestions against your codebase, evaluate technical soundness, respond with clarity, and implement one item at a time with testing. This prevents misunderstandings and rework.
Apply item-by-item verification and testing across diverse codebases and languages using a rigorous feedback evaluation process. This technical approach maintains code quality standards regardless of team structure or technology stack.
Yes. By validating feedback for technical correctness and driving changes with verification and testing, you catch and address unclear or misinformed suggestions early, eliminating rework and improving overall development velocity.
srogouskiReview code changes for quality, maintainability, and correctness with actionable feedback.
beekeeper-labPromote a test branch to main via pull request after tests and lint pass.
baasith6Document technical decisions using structured Architecture Decision Records with sequential numbering.
inbharataiAnalyzes code for bugs, security vulnerabilities, performance bottlenecks, and style violations.
