skills.rest
ben-mad-jlp
ben-mad-jlpCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Convert vague code-review feedback into verified, incremental implementation steps.

Updated Jan 12, 2026
Search Tags:#clarification#best-practices#pushback#code-review#software-engineering#technical-verification
One-click install
npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill receiving-code-review-ben-mad-jlp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ben-mad-jlp/claude-mermaid-collab/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill receiving-code-review-ben-mad-jlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers handle code-review feedback with rigorous verification before implementing changes.

Core Features & Use Cases

  • Clarifying questions: Restate requirements and ask for ambiguity when feedback is unclear.
  • Technical verification: Check against codebase realities before accepting changes.
  • Incremental implementation: Respond with a plan and implement one item at a time, testing each change.

Quick Start

Provide a thoughtful, technically grounded reply to the reviewer, starting with the restatement of the requirement and a plan to verify it.

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 vague or conflicting code-review feedback?▼

To respond to vague code-review feedback, restate the requirement for clarification, verify the suggestion against the codebase, and implement changes incrementally with testing to ensure technical accuracy.

What is the best way to push back on a code review comment?▼

The best way to push back on a code review comment is to technically verify the feedback against codebase realities first, then provide a clear, grounded response explaining your reasoning before refusing the change.

How do I turn unclear pull request comments into actionable steps?▼

Turn unclear pull request comments into actionable steps by applying a six-step workflow: read, understand, verify, evaluate, respond, and implement, ensuring each change is test-driven and incremental.

How should I implement code review changes for bug fixes and feature refinements?▼

Implement code review changes for bug fixes and feature refinements by responding with a verification plan first, then applying incremental, test-driven updates one item at a time to maintain software stability.

When should I ask for clarification during a software engineering code review?▼

Ask for clarification during a software engineering code review whenever feedback is ambiguous or conflicting, allowing you to accurately restate requirements before proceeding with technical verification and implementation.

Does this code review workflow require any specific testing frameworks or dependencies?▼

No specific testing frameworks or dependencies are required; the workflow focuses on promoting incremental, test-driven changes and rigorous technical verification regardless of your software engineering stack.

Related Skills

Explore More Software Engineering Skills→
ClyptAIClyptAI

receiving-code-review

Restate code-review feedback, verify against the repository, and implement changes incrementally with tests.

Official
Advanced
sommiosommio
1

ce:work

Automate plan-driven work execution with testing and incremental commits.

Community
Advanced
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
inbharataiinbharatai
22

code-reviewer

Analyzes code for bugs, security vulnerabilities, performance bottlenecks, and style violations.

Community
Advanced