skills.rest
Suara17
Suara17COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify code-review feedback against requirements before implementing changes one by one.

Updated Jan 12, 2026
Search Tags:#workflow#verification#clarification#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/Suara17/guanlan-sina --skill receiving-code-review-suara17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Suara17/guanlan-sina/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/Suara17/guanlan-sina --skill receiving-code-review-suara17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers to handle code-review feedback by verifying requirements before implementing changes.

Core Features & Use Cases

  • Structured feedback handling: Restate requirements, Verify against codebase reality, and Implement one item at a time.
  • Clear pushback and questions: Ask clarifying questions when items are unclear, avoid performative agreement.
  • Workflow-driven: Apply a deterministic six-step process to ensure technical correctness.

Quick Start

Use this skill to respond to a code review by reading the feedback, restating the requirement, and initiating one verified change at a time.

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 that seems technically questionable?▼

To handle technically questionable code review feedback, verify the requirements against the codebase reality and push back with technical reasoning before implementing any changes.

What is the best way to clarify unclear code review comments on a pull request?▼

The best way to clarify unclear code review comments is to restate the requirements and ask clarifying questions, avoiding performative agreement until validation is complete.

How do I implement code review changes one by one?▼

Implement code review changes one by one by following a deterministic six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT each item sequentially.

When should I push back on code review feedback?▼

You should push back on code review feedback when the items are unclear or technically questionable, using technical reasoning to evaluate and validate the requirements before agreeing.

Does this code review workflow block agreement before verification?▼

Yes, this code review workflow blocks performative agreement until validation is complete, ensuring you restate requirements and verify against codebase reality first.

Related Skills

Explore More Software Engineering Skills→
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
dungsnowaxedungsnowaxe

openspec-apply-change

Implement OpenSpec change tasks sequentially and track progress.

Community
Advanced
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
qvidal01qvidal01

ship

Automate CI/CD merge and deployment for GitHub pull requests.

Community
Advanced