engineering-review-feedback — Claude Code skill: code review handling
engineering-review-feedback — a skill that teaches the agent to handle reviewer comments as the change author: apply fixes, draft replies, resolve disagreements.
MIT 124 installs ★ 635 updated 2026-09-29
npx skills add agentara/skills --skill engineering-review-feedback -a claude-codeWhat engineering-review-feedback does
The skill gives the agent a workflow for processing code review feedback. It teaches the agent to classify comments (code change required, test change required, clarification needed, disagreement to discuss), fix the code so future readers benefit rather than just explain in the review thread. When a reviewer does not understand the code, the agent simplifies the code or renames entities first, and only then adds a comment.
Includes reply templates for agreement, disagreement, and clarification scenarios. For disagreements, the agent compares tradeoffs rather than rejecting the person. Requires no FFmpeg, extra libraries, or API keys — the skill works in any editor from the list.
Adapted from Google Engineering Practices Documentation under CC-BY 3.0.
What it helps with
- apply reviewer comments to code and tests
- draft a reply to a pull request comment
- resolve technical disagreement with a reviewer
- clarify unclear requirement from review
- summarize what changed after a feedback round
Example prompts for the agent
- Apply the reviewer's comments from the last thread.
- Reviewer asks to rename
validateUser— what should I reply and how do I fix it? - I disagree with moving retry to a separate layer, draft a reply with reasoning.
How to install engineering-review-feedback
1Skills CLI (Vercel)
npx skills add agentara/skills --skill engineering-review-feedback -a claude-code2Manually: put the files in place
~/.claude/skills/engineering-review-feedback/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/engineering-review-feedback/
1Skills CLI (Vercel)
npx skills add agentara/skills --skill engineering-review-feedback -a codex2Manually: put the files in place
.agents/skills/engineering-review-feedback/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add agentara/skills --skill engineering-review-feedback -a cursor2Manually: put the files in place
.cursor/skills/engineering-review-feedback/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install agentara/skills skills/engineering/engineering-review-feedback2Manually: put the files in place
.github/skills/engineering-review-feedback/SKILL.md1Skills CLI (Vercel)
npx skills add agentara/skills --skill engineering-review-feedback -a gemini-cli2Platform CLI
gemini skills install https://github.com/agentara/skills --path skills/engineering/engineering-review-feedbackManually: put the files in place
.devin/skills/engineering-review-feedback/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add agentara/skills --skill engineering-review-feedback -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about engineering-review-feedback
How to install engineering-review-feedback in Claude Code?
Run npx skills add agentara/skills --skill engineering-review-feedback -a claude-code, the skill appears at ~/.claude/skills/engineering-review-feedback/SKILL.md.
What does engineering-review-feedback do?
The skill teaches the agent to handle code review comments as the change author: classify feedback, fix code, draft replies, and resolve disagreements with reviewers.
When does the agent trigger this skill?
Triggers: "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", "apply PR comments". If the role is unclear, the agent asks whether you are the author or reviewer.
Source text
SKILL.md · MIT
--- name: engineering-review-feedback description: > Use when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested. --- # Engineering Review Feedback Handle reviewer feedback as collaboration toward better code. The best response often changes the code, tests, or comments so future readers benefit, rather than explaining only inside the review thread. Adapted from Google Engineering Practices Documentation, especially "How to handle reviewer comments." Source: <https://google.github.io/eng-practices/review/developer/handling-comments.html>. License: CC-BY 3.0. ## Response Workflow 1. Pause before responding if the comment feels frustrating. 2. Identify what the reviewer is asking for. 3. Classify each comment: - Code change required. - Test change required. - Documentation or comment change required. - Clarification needed. - Disagreement to discuss. - Non-blocking suggestion. 4. Prefer improving the artifact over explaining in the review tool. 5. Run the relevant verification. 6. Reply with what changed, why, and how it was tested. If a reviewer says they do not understand the code, first try to make the code clearer. Add a code comment only when the why cannot be expressed cleanly in code. ## When You Agree Use a short response and make the change. ```text Done. I renamed the helper to describe normalization rather than validation and updated the two call sites. Tested with: npm test -- user-profile.test.ts ``` ## When You Need Clarification Ask for the missing decision or constraint. Avoid defensive wording. ```text I want to make sure I understand the concern. Are you asking for this to reject duplicate requests at the API boundary, or for the worker to make duplicate processing idempotent? ``` ## When You Disagree Disagree by comparing tradeoffs, not by rejecting the person. ```text I chose X because it keeps the retry policy in one place and avoids a second queue state. My concern with Y is that it makes cancellation observable in two different layers. If you think Y better serves the rollback requirement, I can switch to it. Is that the tradeoff you want prioritized? ``` If the reviewer provides better technical reasoning, accept it and adjust. If neither side can converge, move to a higher-bandwidth conversation and summarize the decision back in the review. ## When Feedback Is Not Constructive Do not reply in kind. Extract any technical concern that can be addressed in code, tests, or docs. If the comment is hostile, vague, or repeatedly unproductive, move to a private or higher-bandwidth conversation, involve a lead when needed, and summarize only the technical decision back in the review. ## Fix the Right Place - Confusing expression: simplify or rename it. - Hidden invariant: encode it in types, validation, assertions, or a focused comment. - Missing behavior confidence: add or improve tests. - Missing context: update the PR description, code comment, README, or design doc. - Reviewer misunderstanding caused by stale diff: rebase, remove dead code, or update the description. - Pure preference: ask whether it is required; otherwise treat as optional. ## Summary Reply Template ```markdown Addressed this round: - Changed ... - Added/updated tests for ... - Clarified ... Verification: - `...` Open: - ... ``` ## Common Mistakes - Replying in anger or with sarcasm. - Explaining confusing code only in the review thread. - Treating every reviewer suggestion as mandatory without clarifying severity. - Saying "will clean up later" when the current change introduces the complexity. - Making broad unrelated refactors while addressing a narrow review comment.
© agentara · MIT · agentara/skills