skills.rest
hetsheth-droid
hetsheth-droidCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Mar 31, 2026
Search Tags:#quality-gate#code-review#decision-making#pull-request#feedback-handling#technical-verification
One-click install
npx skills add https://github.com/hetsheth-droid/toolbox-template --skill receiving-code-review-hetsheth-droid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/superpowers-skills/receiving-code-review
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill receiving-code-review-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach for handling code review feedback to ensure technical rigor and avoid performative agreement.

Core Features & Use Cases

  • Systematic feedback processing: read, understand, verify, evaluate, respond, and implement in controlled steps.
  • Clarification-first: when feedback items are unclear, ask for details before acting.
  • Guardrails for reviewers and contributors: prevent blind acceptance and promote technically sound decisions.
  • Stepwise implementation: prioritize blocking issues, then simple fixes, then complex changes, with individual testing.

Quick Start

Follow the six-step pattern (read, understand, verify, evaluate, respond, implement) before making any changes 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 code review feedback systematically to avoid blind acceptance?▼

Handle code review feedback by applying a six-step pattern: read, understand, verify, evaluate, respond, and implement. This ensures decisions are based on technical verification rather than performative agreement.

What should I do when pull request feedback items are ambiguous or unclear?▼

When pull request feedback items are unclear, ask clarifying questions before acting. This clarification-first approach prevents misinterpreting review comments and ensures technically sound decisions.

What is the best way to implement multiple changes requested in a code review?▼

Implement multiple code review changes stepwise by prioritizing blocking issues first, then simple fixes, and finally complex changes. Test each controlled modification individually to maintain quality.

How do I evaluate technical feedback on a pull request without social bias?▼

Evaluate technical feedback on a pull request by verifying the code reality against the reviewer's comments. This technical verification step separates valid technical constraints from subjective social cues.

Can I use this structured feedback handling process for complex software projects?▼

Yes, you can use this structured feedback handling process across software projects of varying complexity. It handles multi-item feedback to maintain quality and consistency through controlled, testable changes.

Related Skills

Explore More Software Engineering Skills→
PoseidoncodePoseidoncode

receiving-code-review

Evaluate code review feedback against codebase requirements before implementation.

Community
Intermediate
mvillmowmvillmow
18

gh-fix-pr-feedback

Fetch GitHub PR review comments, implement changes, and reply to each comment.

Community
Basic
zpyoungzpyoung
4

receiving-code-review

Guide code review feedback response with verification and clarification steps.

Community
Intermediate
xvawlxvawl
1

pre-merge-checklist

Validate Python and TypeScript PRs against linting, typing, tests, and documentation.

Community
Intermediate