skills.rest
miptah21
miptah21COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Restate and verify code review feedback before implementing changes sequentially.

2|Updated Apr 8, 2026
Search Tags:#code review#regression testing#technical verification#clarifying questions#implementation order#pushback on feedback
One-click install
npx skills add https://github.com/miptah21/skills --skill receiving-code-review-miptah21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/miptah21/skills --skill receiving-code-review-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect, performative, or risky changes by ensuring code review feedback is understood and technically verified before implementation.

Core Features & Use Cases

  • Clarify and verify first: Reads feedback fully, restates requirements, and checks them against the actual codebase before acting.
  • Avoid performative agreement: Replaces praise-based responses with technical acknowledgment, reasoned pushback, or targeted questions.
  • Safe, ordered changes: Implements multi-item feedback one-by-one, testing each fix and prioritizing blocking/security issues.

Quick Start

Use the receiving-code-review skill when handling incoming code review comments so you can restate unclear items, verify technical correctness against the repository, and only then implement changes item-by-item 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 code review feedback before making any code changes?▼

Yes, you should push back on code review feedback using technical reasoning when the suggestions are incorrect, ensuring you avoid performative agreement and maintain codebase integrity through technical verification.

What is the best way to implement multi-item code review comments?▼

The best way to implement multi-item code review comments is sequentially, executing changes one-by-one, prioritizing blocking and security issues, and running tests after each individual fix to ensure safe implementation.

When should I ask clarifying questions during a code review?▼

You should ask clarifying questions during a code review when scope, context, or correctness is uncertain, stopping for clarification instead of guessing to ensure full comprehension of the requested changes.

How to avoid performative agreement when responding to pull request reviews?▼

Avoiding performative agreement involves replacing praise-based responses with technical acknowledgment, reasoned pushback, or targeted questions that demonstrate actual comprehension of the reviewer's suggestions.

Does this approach work for external reviewer suggestions on internal pull requests?▼

Yes, this approach works for internal pull request reviews, external reviewer suggestions, and multi-item comment threads where scope, context, or correctness may be uncertain and require technical verification.

Related Skills

Explore More Software Engineering Skills→
chokky-educationchokky-education

receiving-code-review

Standardizes incoming code review feedback verification and technical response preparation for pull requests and peer sessions.

Community
Intermediate
beshkenadzebeshkenadze
3

verify-known-issues

Verifies suspected bugs or limitations in external software via web search and citation-first reporting.

Community
Intermediate
rivaldiekaptrrrrivaldiekaptrrr

eval-harness

Define and run eval suites to validate AI task performance.

Community
Advanced
microsoftmicrosoft
561

code-style

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

Official
Intermediate