skills.rest
mliudev
mliudevCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Triage code review feedback and implement approved changes in focused batches.

Updated Apr 21, 2026
Search Tags:#testing#feedback#implementation#clarification#review#code-review#decision-making
One-click install
npx skills add https://github.com/mliudev/agent-workflows --skill receiving-code-review-mliudev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mliudev/agent-workflows/tree/main/skills/claude/receiving-code-review
Command: npx skills add https://github.com/mliudev/agent-workflows --skill receiving-code-review-mliudev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handle review feedback with technical rigor: clarify, verify, decide, implement, and re-test instead of agreeing blindly. Use when the user shares review comments from a reviewer, teammate, or GitHub PR and wants help deciding what to change.

Core Features & Use Cases

  • Clarify ambiguous items before implementing any feedback.
  • Evaluate each suggestion against the codebase and requirements.
  • Implement changes in focused batches, with re-testing to confirm you addressed the issue.

Quick Start

Summarize the review, clarify ambiguities, propose changes, implement the approved fixes, and re-test to confirm the outcome.

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 without blindly accepting changes?▼

Handle code review feedback by clarifying ambiguous items, evaluating suggestions against requirements, and implementing approved changes in focused batches. Re-test your code to confirm the fix addresses the reviewer's issue.

What is the best way to triage GitHub PR review comments?▼

Triage GitHub PR review comments by identifying actionable feedback, verifying it against the codebase, and deciding whether to implement the change or request clarification before proceeding with focused updates.

How do I implement code review suggestions in focused batches?▼

Implement code review suggestions in focused batches by evaluating each comment, grouping related fixes, applying the changes, and running tests to validate that each batch resolves the feedback without introducing regressions.

When should I ask for clarification on a teammate's code review?▼

Ask for clarification on a teammate's code review when feedback is ambiguous, conflicts with existing requirements, or lacks sufficient context to determine the correct implementation approach before making any changes.

Can I use this process for external code reviews outside my team?▼

Yes, you can use this process for external code reviews. The workflow applies to review comments from teammates, GitHub PRs, and external reviewers to guide clarification, decision-making, and implementation.

Why re-test code after implementing review feedback?▼

Re-test code after implementing review feedback to validate that the applied changes correctly resolve the identified issues and respect the original specifications without breaking existing functionality.

Related Skills

Explore More Software Engineering Skills→
BrOrlandiBrOrlandi
20

pr-review

Fetches GitHub pull-request review comments and categorizes them by urgency and type.

Community
Advanced
bbohhu-progbbohhu-prog

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
monforjemonforje

golang-code-style

Evaluate Go code against golangci-lint style guidelines.

Community
Intermediate