receiving-code-review

Classify code-review comments into four categories and generate PR replies.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hbvg234/jnmt.vn --skill receiving-code-review-hbvg234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill receiving-code-review-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You receive review feedback on your code or changes and may struggle to interpret comments, prioritize fixes, or justify decisions. This Skill helps you triage feedback, categorize each item, and justify changes or declines.

Core Features & Use Cases

  • Classification: categorize each comment into Must fix, Should fix, Optional, or Reject-with-reason.
  • Action with evidence: implement changes with clear evidence (diffs or tests) and summarize responses.
  • PR communication: generate a structured reply format to reviewers explaining decisions and next steps.

Quick Start

Analyze the latest PR comments and classify each item into the four categories, then implement and document changes with a concise PR reply.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage code review feedback on a pull request?▼

Code review classification categorizes each comment into must-fix, should-fix, optional, or reject-with-reason. It applies to pull requests and inline review threads, guiding you through addressing changes, negotiating trade-offs, and documenting decisions.

What's the best way to respond to code review comments with evidence?▼

Respond to code review comments by implementing changes with clear evidence, such as diffs or tests, and summarizing responses. This approach requires evidence-backed fixes and outputs a structured PR reply template explaining decisions and next steps to reviewers.

How do I justify rejecting a code review suggestion?▼

Reject a code review suggestion by classifying it as reject-with-reason, documenting your rationale, negotiating trade-offs, and generating a structured PR reply template and change-log trace that explains the decision to reviewers.

Can I use this code review feedback triage process for inline review threads?▼

Yes, the code review feedback triage process applies to inline review threads across codebases. It categorizes each comment into four distinct categories and guides you through addressing changes, negotiating trade-offs, and documenting decisions.

How to generate a PR reply template after addressing review feedback?▼

Generate a PR reply template by classifying review comments, implementing evidence-backed fixes with diffs or tests, and documenting decisions. The process outputs a structured reply format explaining decisions and next steps to reviewers alongside a change-log trace.

What are the limitations of automated code review comment triage?▼

Automated code review triage is limited to classifying comments into must-fix, should-fix, optional, or reject-with-reason categories. It requires evidence-backed fixes like diffs or tests and does not bypass the need for manual implementation and negotiation of trade-offs.