skills.rest
shmily1012
shmily1012COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

1|1|Updated Dec 1, 2025
Search Tags:#debugging#feedback#verification#code-review#pull-request#technical-rigor#push-back
One-click install
npx skills add https://github.com/shmily1012/AutoWriter --skill receiving-code-review-shmily1012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/shmily1012/AutoWriter/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/shmily1012/AutoWriter --skill receiving-code-review-shmily1012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Providing code review feedback is common, but acting without verification can introduce defects. This skill ensures engineers verify requirements, assess technical impact, and avoid performative agreement.

Core Features & Use Cases

  • Six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to ensure changes are justified.
  • Unclear feedback handling: ask for clarifications before acting to prevent wrong changes.
  • Guardrails for external reviews: push back with technical reasoning and verify compatibility with the codebase.
  • YAGNI and safety checks: identify unused suggestions and avoid unnecessary changes.

Quick Start

When you receive code review feedback, read it completely, restate the requirement, verify against the codebase, evaluate technical soundness, respond with technical acknowledgment or reasoned pushback, and implement changes one item 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 without introducing new bugs?▼

Handle code review feedback by applying a six-step process: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This ensures you validate suggestions against the codebase and evaluate technical impact before making any changes.

What is the best way to push back on unclear pull request comments?▼

Push back on unclear pull request comments by asking for clarifications before acting. Use technical reasoning to document your evaluation, ensuring you avoid performative agreement and prevent wrong changes from entering the codebase.

Can I implement code review changes incrementally to reduce integration risk?▼

Yes, you can implement code review changes incrementally by processing feedback one item at a time. This controlled approach requires validating every change against the codebase before final integration to ensure technical safety.

When should I not use performative agreement for code review feedback?▼

Avoid performative agreement when code review feedback is unclear or potentially risky. Instead, apply technical pushback with structured validation, document your reasoning, and verify the requirements before implementing any suggestions.

Related Skills

Explore More Software Engineering Skills→
benjaminshoemakerbenjaminshoemaker
39

create-pr

Create GitHub pull requests with verification and Codex review.

Community
Intermediate
mParticlemParticle
24

verify

Run lint and test suites to validate code changes.

Official
Intermediate
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
aisa-groupaisa-group
90

code-review

Run style checks on Python code and return structured JSON feedback.

Official
Intermediate