skills.rest
nassimbf
nassimbfCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

3|Updated Apr 18, 2026
Search Tags:#verification#risk-assessment#code-review#pull-request#incremental-implementation#feedback-management#technical-clarification
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill receiving-code-review-nassimbf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill receiving-code-review-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often yield ambiguous or unclear feedback. This skill provides a structured approach to verify requirements before implementing changes, reducing misinterpretation and rework.

Core Features & Use Cases

  • Structured feedback handling: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT as a disciplined workflow.
  • Clarification-first approach: prioritizes asking clarifying questions before making changes to ensure alignment.
  • Risk-aware decision making: includes checks for impact, compatibility, and rationale to justify actions.

Quick Start

Read feedback carefully, ask clarifying questions, and verify against the codebase before implementing.

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 ambiguous code review feedback on a pull request?▼

Handle ambiguous code review feedback by applying a structured workflow: read, understand, verify against the codebase, evaluate technical impact, and respond before implementing changes. This clarification-first approach prevents misinterpretation and reduces rework.

What is the best way to verify technical requirements before implementing code changes?▼

Verifying technical requirements before implementation involves assessing risk, checking codebase compatibility, and evaluating the rationale behind the feedback. This structured critique workflow ensures controlled, incremental changes aligned with project goals.

How do I ask clarifying questions when code review comments are unclear?▼

Ask clarifying questions by restating the feedback, verifying the context against the existing codebase, and evaluating the technical impact. This risk-aware decision-making process ensures alignment before any incremental implementation begins.

Does a structured code review workflow help with conflicting pull request feedback?▼

A structured code review workflow manages conflicting feedback by enforcing verification and technical evaluation before implementation. It prioritizes restatement and risk assessment to justify actions and resolve conflicts through controlled changes.

When should I not use an incremental implementation approach for code review changes?▼

Avoid incremental implementation when feedback lacks technical clarity or when risk assessment reveals high compatibility impact. The workflow requires successful verification and technical evaluation of the rationale before proceeding with any code changes.

Related Skills

Explore More Software Engineering Skills→
picassiopicassio
48

squad-code-review

Review source code with two-pass correctness and complexity assessment.

Community
Intermediate
galangryandanagalangryandana
20

receiving-code-review

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

Community
Basic
mbwsimsmbwsims
71

hotspots

Identify high-risk files in a codebase using churn, complexity, and coupling.

Community
Intermediate
zpyoungzpyoung
4

receiving-code-review

Guide code review feedback response with verification and clarification steps.

Community
Intermediate