skills.rest
nandkapadia
nandkapadiaCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Jan 16, 2026
Search Tags:#verification#synthesis#code-review#guardrails#pull-request#technical-rigor
One-click install
npx skills add https://github.com/nandkapadia/claude-skills-agents --skill receiving-code-review-nandkapadia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/nandkapadia/claude-skills-agents/tree/main/copilot/skills/receiving-code-review
Command: npx skills add https://github.com/nandkapadia/claude-skills-agents --skill receiving-code-review-nandkapadia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures rigorous, structured responses to code-review feedback by verifying changes against the codebase before applying them, and by resisting performative agreement.

Core Features & Use Cases

  • Verify feedback against the repository to confirm what needs changing.
  • Synthesize actionable issues and guidance to fix problems in code, comments, or tests.
  • Provide pushback with technical reasoning when feedback is unclear or risky.

Quick Start

Review incoming code-review comments and respond with precise, evidence-based justifications for proposed 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 respond to code review feedback with technical rigor?▼

Handling code review feedback rigorously involves verifying reviewer claims against the codebase before refactoring, synthesizing actionable issues, and pushing back with technical reasoning when suggestions are unclear or risky.

How do I verify code review comments against my codebase before refactoring?▼

Verifying code review comments against your codebase requires checking the specific files and logic mentioned in the feedback to confirm the issue exists, ensuring you only implement refactors for validated, actionable problems.

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

The best way to push back on unclear pull request feedback is to provide structured, technical reasoning. Instead of performative agreement, demand clarification and cite codebase evidence to highlight risks or contradictions in the review.

How do I synthesize code review issues for staged implementation?▼

Synthesize code review issues by grouping feedback into actionable categories, verifying each claim against the repository, and applying structured response patterns to execute subsequent refactors in logical, staged implementation phases.

Does this approach work for feedback from automated models and human reviewers?▼

Yes, this approach works for feedback from both automated models and human reviewers. It guides the synthesis of issues and subsequent refactors by enforcing technical verification of claims against the codebase regardless of the feedback source.

Related Skills

Explore More Software Engineering Skills→
SuperCorksSuperCorks

address-pr-comments

Fetch GitHub PR reviews via gh CLI and apply latest reviewer feedback.

Community
Advanced
yabafreyabafre
2

aped-receive-review

Convert code review comments into verified, item-by-item implementation decisions.

Community
Advanced
benchflow-aibenchflow-ai
317

code-cleanup

Identify and verify dead code and latent bugs in Python codebases.

Official
Advanced
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate