skills.rest
Chikage0o0
Chikage0o0COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluates code review feedback and implements verified, incremental changes.

34|6|Updated Jan 19, 2026
Search Tags:#verification#clarification#best-practices#pushback#code-review#technical-rigor
One-click install
npx skills add https://github.com/Chikage0o0/opencode --skill receiving-code-review-chikage0o0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Chikage0o0/opencode/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/Chikage0o0/opencode --skill receiving-code-review-chikage0o0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured approach to handling code review feedback, ensuring changes are verified, not performatively agreed to, and implemented with technical rigor.

Core Features & Use Cases

  • Read feedback completely: Read feedback in full before reacting.
  • Restate and clarify requirements: Restate requirements or ask clarifying questions.
  • Verify against codebase reality: Check that proposed changes align with current code and tests.
  • Evaluate technical soundness: Assess whether the suggested changes are appropriate for THIS codebase.
  • Respond with technical rationale or pushback: Provide reasoned acknowledgment or a well-argued pushback.
  • Implement iteratively and test: Apply changes one item at a time and verify.
  • Real-world use-case-oriented handling: When feedback references multiple items, validate scope and prioritize issues before implementing.

Quick Start

Clarify any unclear items with the reviewer, then implement changes one by one after verifying their impact.

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 is unclear or technically questionable?▼

Handle unclear code review feedback by reading it completely, restating requirements, and verifying suggestions against the codebase reality before implementing any incremental changes. Ask clarifying questions to resolve ambiguities.

What is the best way to push back on a code review suggestion?▼

The best way to push back on code review suggestions is to evaluate their technical soundness against the current codebase, then respond with a well-argued technical rationale explaining why the proposed changes are inappropriate.

How do I implement code review changes iteratively and test them?▼

Implement code review changes iteratively by applying feedback one item at a time, verifying the impact of each change against current tests, and validating the scope and prioritizing issues before implementation.

When should I not just agree to code review feedback?▼

You should not performatively agree to code review feedback when suggestions lack technical accuracy. Always verify proposed changes align with codebase reality and evaluate technical soundness before taking action.

How do I evaluate technical soundness of feedback for my specific codebase?▼

Evaluate technical soundness by checking that proposed changes align with current code and tests, assessing whether the suggestions are appropriate for your specific codebase, and validating the scope of referenced items.

Related Skills

Explore More Software Engineering Skills→
bonnguyenitcbonnguyenitc
19

receiving-code-review

Triage and respond to code review feedback with verification and prioritized fixes.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

fix-tests

Diagnose and repair failing test suites across multiple language ecosystems.

Community
Advanced
scruffydanscruffydan

receiving-code-review

Interpret and validate code-review feedback against the codebase before implementing changes.

Community
Basic
NabilThangeNabilThange
1

i18n-localization

Detect hardcoded strings and manage translations for software localization.

Community
Advanced