skills.rest
artgaurav16420-oss
artgaurav16420-ossCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Clarify and verify code-review feedback against the codebase before implementing changes.

Updated May 2, 2026
Search Tags:#communication#verification#code-review#decision-making#pull-requests#technical-rigor
One-click install
npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill receiving-code-review-artgaurav16420-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/artgaurav16420-oss/Mega-Skills/tree/main/distribution/harnesses/tabnine/agent/skills/receiving-code-review
Command: npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill receiving-code-review-artgaurav16420-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback is often unclear or subjective. This Skill helps ensure feedback is understood, verified, and acted on with technical rigor before any changes are implemented.

Core Features & Use Cases

  • Clarify requirements: Restate and confirm the exact needs from the feedback.
  • Verification against codebase: Check that suggested changes align with current code, tests, and project constraints.
  • Incremental implementation: Apply feedback item by item, validating each change with tests and reasoning.
  • Pushback with technical reasoning: Provide reasoned resistance when feedback is ambiguous or unsafe.

Quick Start

Begin by asking clarifying questions about any unclear item in the code-review feedback and verify the requirement against the repository state.

Frequently Asked Questions about receiving-code-review

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

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

Verify code-review feedback by restating requirements, validating suggestions against the current codebase and tests, and ensuring changes align with project constraints before implementation.

What is the best way to handle ambiguous or conflicting code-review comments on pull requests?▼

Handle ambiguous code-review comments by asking clarifying questions, confirming exact requirements, and documenting the technical rationale before proceeding with incremental changes.

How do I push back on code-review feedback that seems technically incorrect?▼

Push back on incorrect code-review feedback by validating the suggestion against repository state and providing reasoned resistance supported by technical rigor and codebase evidence.

Can I apply code-review feedback incrementally across multiple pull requests?▼

Apply code-review feedback incrementally by addressing each item individually, validating every change with tests and reasoning, and documenting the rationale for safe implementation.

When should I clarify code-review requirements instead of directly implementing them?▼

Clarify code-review requirements whenever feedback is unclear, subjective, or conflicts with existing code, ensuring technical correctness by validating against the codebase first.

Related Skills

Explore More Software Engineering Skills→
russosalvrussosalv
5

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:py-test

Run pytest tests with coverage enforcement for Python code changes.

Official
Intermediate
joseph-c-mcguirejoseph-c-mcguire
1

06-tech-tooling

Set up and validate linters, formatters, and test runners for CI builds.

Community
Advanced
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate