skills.rest
pantheon-org
pantheon-orgOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback through a six-step workflow before implementation.

1|Updated Dec 5, 2025
Search Tags:#workflow#communication#verification#clarification#code-review#incremental-implementation#technical-rationale
One-click install
npx skills add https://github.com/pantheon-org/opencode-plugins --skill receiving-code-review-pantheon-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/pantheon-org/opencode-plugins/tree/main/.opencode/skills/recieving-code-review
Command: npx skills add https://github.com/pantheon-org/opencode-plugins --skill receiving-code-review-pantheon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers handle code review feedback with discipline, ensuring verification before implementation to avoid misinterpretation and unnecessary rework.

Core Features & Use Cases

  • Clarify requirements: Restate feedback in precise terms to confirm intent.
  • Technical verification: Compare feedback against the codebase and project standards.
  • Controlled execution: Push back with technical reasoning when feedback is unclear and implement items one at a time with tests.
  • Risk reduction: Prevent blind agreement and reduce regression risk by incremental changes.

Quick Start

When you receive feedback, read it completely, restate the requirement if unclear, verify against the codebase, evaluate technical correctness, respond with rationale, and begin implementing items one by one with tests.

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

Handle unclear code review feedback by restating the requirement to confirm intent, verifying against the codebase, and seeking clarification before acting. This prevents misinterpretation and unnecessary rework.

What is the best way to implement code review comments safely?▼

The best way to implement code review comments safely is through a six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces incremental changes with tests to reduce regression risk.

How does verification before implementation improve code review responses?▼

Verification before implementation improves code review responses by comparing feedback against project standards and technical facts. This allows you to push back with technical reasoning instead of blind agreement, reducing regression risk.

Can I push back on technically questionable code review feedback?▼

Yes, you can push back on technically questionable code review feedback by evaluating its technical correctness against the codebase. You should respond with clear technical rationale and seek clarification for ambiguous items before implementing changes.

Why should I implement code review items one at a time with tests?▼

You should implement code review items one at a time with tests to ensure controlled execution and reduce regression risk. This incremental implementation approach maintains codebase stability while verifying each change independently.

Related Skills

Explore More Software Engineering Skills→
minhhhminhhh

receiving-code-review

Guide engineers through a six-step code review feedback process with testing.

Community
Advanced
findexufindexu
1

refactor

Refactor code incrementally with tests, lint, and typecheck verification.

Community
Intermediate
artgaurav16420-ossartgaurav16420-oss

receiving-code-review

Clarify and verify code-review feedback against the codebase before implementing changes.

Community
Advanced
microsoftmicrosoft
561

code-style

Enforce Python code style with black, flake8, and mypy.

Official
Intermediate