skills.rest
kckylechen1
kckylechen1COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Process code review feedback through a six-step verification pattern.

Updated Jan 28, 2026
Search Tags:#verification#quality#process#pushback#code-review#technical-reasoning
One-click install
npx skills add https://github.com/kckylechen1/ai-agent-toolkit --skill receiving-code-review-kckylechen1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/kckylechen1/ai-agent-toolkit/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/kckylechen1/ai-agent-toolkit --skill receiving-code-review-kckylechen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process code review feedback with technical rigor and verified reasoning.

Core Features & Use Cases

  • Six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to handle feedback systematically.
  • Guardrails: No performative agreement; require verification and justification before changes.
  • Use Case: When feedback is unclear or potentially technically questionable, this skill guides you to ask clarifying questions and push back with technical reasoning.

Quick Start

Apply the six-step pattern to the latest feedback to determine the correct next action without rushing to code.

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 unclear or technically questionable code review feedback?▼

To handle unclear code review feedback, apply a rigorous verification process before implementing changes. This involves reading, understanding, and verifying the technical reasoning to justify modifications, preventing performative agreement.

What is the best way to push back on code review comments with technical reasoning?▼

The best way to push back on code review comments is through verified technical reasoning. Evaluate the feedback systematically to ensure changes are justified and tested, avoiding performative agreement when the feedback is technically questionable.

How do I process code review feedback systematically before writing code?▼

Process code review feedback systematically by applying a six-step pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This guides you through verification and justification before making any code changes.

When do I need to verify technical reasoning before implementing code review changes?▼

You need to verify technical reasoning before implementing code review changes whenever feedback is unclear or technically questionable. This ensures guardrails are met, requiring justification and testing before modifications are applied.

Why does performative agreement hurt code review quality?▼

Performative agreement hurts code review quality because it bypasses technical verification. Implementing unjustified changes without rigorous evaluation introduces potential errors, making verified reasoning essential for maintaining quality.

Related Skills

Explore More Software Engineering Skills→
ironbobironbob

receiving-code-review

Process code review feedback through a six-step verification workflow.

Community
Advanced
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic
I-OnlabsI-Onlabs
3

code-auditor

Audit codebases across architecture, quality, security, and performance to produce prioritized health reports.

Community
Advanced
passionseedpassionseed
2

receiving-code-review

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

Official
Intermediate