skills.rest
bjconlan
bjconlanCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Aug 27, 2026
Search Tags:#verification#clarification#pushback#code-review#pull-request#technical-rigor
One-click install
npx skills add https://github.com/bjconlan/burndown --skill receiving-code-review-bjconlan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bjconlan/burndown/tree/main/.gemini/skills/receiving-code-review
Command: npx skills add https://github.com/bjconlan/burndown --skill receiving-code-review-bjconlan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers navigate unclear or questionable code-review feedback by enforcing a structured, verification-first approach that prevents blind agreement or premature changes.

Core Features & Use Cases

  • Structured evaluation: Read, understand, verify, evaluate, respond, and implement items one at a time.
  • Question-driven clarification: Identify ambiguities and request clarifications to avoid misinterpretation.
  • Technical pushback: Provide reasoned, codebase-specific feedback when suggestions are unsafe or unnecessary.

Quick Start

Ask for clarification on unclear feedback and push back with technical reasoning before implementing changes.

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 ambiguous code review feedback on a pull request?▼

Handle ambiguous code review feedback by enforcing a verification-first approach that reads the comment, verifies against the codebase, and requests clarification before implementing any changes. This prevents blind agreement or premature modifications.

What is the best way to push back on technically incorrect code review comments?▼

The best way to push back on technically incorrect code review comments is to provide reasoned, codebase-specific feedback. Verify the suggestion against your code first, then respond with technical rationale explaining why the change is unsafe or unnecessary.

How do I structure my response when evaluating questionable code review suggestions?▼

Structure your response by following a repeatable process: read the feedback, understand the requirement, verify against the codebase, evaluate technical correctness, respond with rationale, and implement changes incrementally one item at a time.

When should I ask for clarification on code review feedback instead of just making the change?▼

Ask for clarification on code review feedback whenever the suggestion is unclear or technically questionable. Requesting clarification avoids misinterpretation and ensures you do not introduce unsafe or unnecessary modifications to the codebase.

Can I apply a structured code review process to any software project?▼

Yes, you can apply this structured code review process to any software project. The verification-first approach is designed to work across projects, ensuring clarity and safe pushback regardless of the specific codebase or platform.

Related Skills

Explore More Software Engineering Skills→
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
databrickslabsdatabrickslabs
38

receiving-code-review

Evaluate code review feedback with structured verification and YAGNI checks.

Official
Intermediate
thavirak-svaythavirak-svay
1

receiving-code-review

Verify code review feedback against the codebase before implementation.

Community
Advanced