skills.rest
SteamedFish
SteamedFishCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Evaluate and respond to code review feedback with technical verification.

6|Updated Jan 14, 2020
Search Tags:#code review#feedback#implementation#verification#technical rigor#pushback
One-click install
npx skills add https://github.com/SteamedFish/dotfiles --skill receiving-code-review-steamedfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/SteamedFish/dotfiles/tree/main/.config/opencode/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/SteamedFish/dotfiles --skill receiving-code-review-steamedfish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you navigate code review feedback by ensuring you technically verify suggestions before blindly implementing them, preventing wasted effort and potential regressions.

Core Features & Use Cases

  • Technical Verification: Ensures feedback is technically sound and relevant to the current codebase.
  • Reasoned Pushback: Empowers you to question or reject feedback with technical justification.
  • Structured Implementation: Guides the order of implementation for multiple feedback items.
  • Use Case: When a reviewer suggests a change that seems unnecessary or potentially harmful, this Skill prompts you to verify its impact and ask clarifying questions rather than immediately coding.

Quick Start

When receiving code review feedback, verify its technical correctness before implementing any suggestions.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate code review feedback before implementing changes?▼

Evaluate code review feedback by applying a structured process for technical verification before implementation. This ensures suggestions are technically sound and relevant, preventing wasted effort and regressions from blindly applying unnecessary changes.

When should I pushback on code review comments?▼

Pushback on code review comments when suggestions are unnecessary or potentially harmful. Reasoned pushback empowers you to question or reject feedback with technical justification, prioritizing technical rigor over performative agreement to maintain codebase integrity.

How do I handle unclear code review feedback or external reviewer suggestions?▼

Handle unclear code review feedback by asking clarifying questions rather than immediately coding. This structured evaluation process addresses unclear feedback and external reviewer suggestions by verifying their impact and technical correctness against the current codebase.

What is the best way to acknowledge incorrect code review pushback?▼

Acknowledge incorrect code review pushback by following a strict protocol for gracefully correcting prior pushback. This enforces a structured process that ensures you acknowledge correct feedback while maintaining technical rigor in your responses.

How do I structure the implementation of multiple code review changes?▼

Structure the implementation of multiple code review changes by following a guided order of implementation. This structured approach ensures feedback items are processed methodically, applying YAGNI principles to avoid implementing unnecessary features.

Related Skills

Explore More Software Engineering Skills→
stabilefrisurstabilefrisur

receiving-code-review

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

Community
Advanced
ditchallawayditchallaway
1

receiving-code-review

Verify code-review feedback against codebase and tests before implementing changes.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced