skills.rest
fernandoxavier02
fernandoxavier02COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated Aug 27, 2026
Search Tags:#verification#quality-assurance#code-review#software-engineering#pull-request
One-click install
npx skills add https://github.com/fernandoxavier02/Superpower-Gemini --skill receiving-code-review-fernandoxavier02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/fernandoxavier02/Superpower-Gemini/tree/main/skills/superpower-receiving-code-review
Command: npx skills add https://github.com/fernandoxavier02/Superpower-Gemini --skill receiving-code-review-fernandoxavier02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback can be ambiguous or technically questionable; this Skill ensures rigorous, verification-based handling before implementing suggestions.

Core Features & Use Cases

  • Verification-first workflow: read, restate, verify against the codebase, and implement items one-by-one.
  • Technical due diligence: checks for conflicts, dependencies, and feasibility; prevents blind agreement.
  • Use Case: during a code-review on a complex feature, you apply the Skill to validate each suggestion and implement only after verification.

Quick Start

When you receive code-review feedback, read it in full, verify each item against the codebase, and implement one item at a time.

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 that seems ambiguous or technically questionable?▼

Handle ambiguous code review feedback by applying a verification-first workflow: read the feedback in full, restate the requirements, verify each item against the codebase, and implement changes one item at a time to prevent misinterpretation.

What is the best way to prevent scope creep when implementing pull request review suggestions?▼

Prevent scope creep during pull request reviews by performing technical due diligence, checking for conflicts and dependencies, and implementing only one verified item at a time rather than blindly agreeing to all suggestions.

How do I push back on a code review comment with technical reasoning?▼

Push back on code review comments by first restating the requirement, verifying the suggestion against the codebase for feasibility, and then providing your technical reasoning before implementing any changes.

Can I use this verification workflow for both feature fixes and refactoring tasks?▼

Yes, you can use this verification-based code review workflow across software engineering teams during pull requests, refactoring tasks, and feature fixes to ensure rigorous handling of feedback.

What steps should I follow to validate code review suggestions before writing code?▼

Validate code review suggestions by following a disciplined sequence: read the feedback, restate the requirements, verify the suggestion against the existing codebase, push back with technical reasoning if needed, and then implement the changes.

Related Skills

Explore More Software Engineering Skills→
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic
yuma588yuma588
2

receiving-code-review

Verifies code review feedback before implementing each requested change step-by-step.

Community
Intermediate
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced
scooter-lacroixscooter-lacroix
8

qlty-during-development

Run qlty check to lint, format, and auto-fix code files.

Community
Basic