skills.rest
vietlinhh02
vietlinhh02COMMUNITY
Explore all skills by this author →
GitHub

Receiving Code Review

Categorize code review feedback into critical, important, and minor issues.

Updated Dec 30, 2025
Search Tags:#workflow#code review#debugging#feedback#collaboration#pull request
One-click install
npx skills add https://github.com/vietlinhh02/cogninote --skill receiving-code-review-vietlinhh02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Receiving Code Review
Source: https://github.com/vietlinhh02/cogninote/tree/main/.claude/skills/methodology/receiving-code-review
Command: npx skills add https://github.com/vietlinhh02/cogninote --skill receiving-code-review-vietlinhh02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to effectively process and respond to code review feedback, ensuring code quality and timely approvals.

Core Features & Use Cases

  • Feedback Categorization: Classify feedback into Critical, Important, and Minor issues.
  • Prioritized Fixing: Guides users to address critical issues first, then important ones, and defer minor suggestions.
  • Re-Review Process: Outlines how to request a re-review after implementing fixes, including a checklist.
  • Disagreement Handling: Offers strategies and templates for respectfully disagreeing with feedback.
  • Use Case: You've just received a PR review with several comments. Use this Skill to categorize them, fix the blocking issues, and prepare a clear summary for the reviewer to request a re-approval.

Quick Start

Use the receiving code review skill to process feedback on your pull request by categorizing issues and planning fixes.

Frequently Asked Questions about Receiving Code Review

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

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

Handle code review feedback by categorizing comments into critical, important, and minor issues. This systematic workflow guides you to prioritize and fix blocking issues first before deferring minor suggestions.

What is the best way to prioritize pull request review comments?▼

Prioritize pull request review comments by classifying them into critical, important, and minor categories. Address critical security and error handling issues first, then important test coverage fixes, and defer minor suggestions.

How do I request a re-review after fixing code review comments?▼

Request a re-review after fixing code review comments by running through a structured checklist. This process ensures all critical and important fixes are implemented and prepares a clear summary for the reviewer to re-approve.

How do I respectfully disagree with code review feedback?▼

Respectfully disagree with code review feedback using provided strategies and templates. This workflow facilitates constructive disagreement resolution while maintaining collaboration and defining clear iteration limits.

What categories should I use to group code review issues?▼

Group code review issues into critical, important, and minor categories. This feedback categorization addresses common types like security, error handling, test coverage, and performance with actionable fixing examples.

Related Skills

Explore More Software Engineering Skills→
as4584as4584
2

requesting-code-review

Dispatch a code reviewer subagent to analyze Git changes and categorize feedback.

Community
Intermediate
jewbetchajewbetcha
115

code-review-checklist

Summarize a code-review checklist covering functionality, quality, security, and performance.

Community
Basic
greyhaven-aigreyhaven-ai
29

grey-haven-code-quality-analysis

Identify code quality issues across files for security reviews and audits.

Community
Basic
jamesjlundinjamesjlundin
32

pr-review

Analyze pull requests and generate structured review reports.

Community
Intermediate