skills.rest
hitsumabushi334
hitsumabushi334COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback through verification and incremental testing.

Updated Jan 20, 2026
Search Tags:#workflow#feedback#verification#quality-assurance#code-review#pull-requests
One-click install
npx skills add https://github.com/hitsumabushi334/KGpaper --skill receiving-code-review-hitsumabushi334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hitsumabushi334/KGpaper/tree/main/.agent/Skills/receiving-code-review
Command: npx skills add https://github.com/hitsumabushi334/KGpaper --skill receiving-code-review-hitsumabushi334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review requires technical evaluation, not emotional performance.

Core Features & Use Cases

  • Structured Evaluation: Verify feedback before implementing changes.
  • Clarification & Validation: Restate requirements and seek clarification when unclear.
  • Incremental Implementation: Tackle feedback item by item with verification and testing.

Quick Start

Read the feedback, restate the requirement in your own words, verify it against the codebase, assess technical correctness, respond with a technical acknowledgment or reasoned pushback, and implement changes one item at a time, testing each.

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?▼

Handling code review feedback requires a structured evaluation: read, restate requirements, verify against the codebase, assess technical correctness, and respond with reasoned pushback before implementing changes incrementally.

What is the correct workflow for responding to pull request comments?▼

The workflow for pull request comments involves reading the feedback, restating the requirement, verifying the suggestion, evaluating correctness, responding technically, and implementing changes item by item with testing.

How do I verify technical correctness of code review suggestions?▼

To verify technical correctness of code review suggestions, restate the requirement in your own words, verify the suggestion against the codebase, and assess its technical validity before implementing the change.

When should I push back on code review feedback?▼

You should push back on code review feedback after verifying the suggestion against the codebase and determining it lacks technical correctness, replacing performative agreement with a reasoned technical response.

What is the best way to implement code review changes incrementally?▼

The best way to implement code review changes incrementally is to tackle feedback item by item, applying verification and testing to each individual change rather than executing all modifications blindly.

Related Skills

Explore More Software Engineering Skills→
mlflowmlflow
1

add-review-comment

Post review comments to GitHub pull requests via the GitHub CLI.

Official
Intermediate
spiralhousespiralhouse
5

baseline-check

Run RuboCop and RSpec checks against previous baselines to detect regressions.

Official
Intermediate
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate
ZateZate
9

vulnerability-patterns

Route codebases to vulnerability-pattern detection skills for security scanning.

Community
Basic