skills.rest
hxk622
hxk622COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Validate incoming code review feedback against the existing codebase.

8|Updated Jan 13, 2026
Search Tags:#code review#feedback#implementation#verification#pushback#technical
One-click install
npx skills add https://github.com/hxk622/TokenDance --skill receiving-code-review-hxk622
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/hxk622/TokenDance/tree/main/backend/app/skills/builtin/superpowers/receiving-code-review
Command: npx skills add https://github.com/hxk622/TokenDance --skill receiving-code-review-hxk622

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified against the codebase before implementation, preventing blind acceptance of potentially incorrect or unnecessary changes.

Core Features & Use Cases

  • Technical Verification: Critically assess feedback for technical correctness and relevance to the specific codebase.
  • Clarification Handling: Request clarification for ambiguous feedback to ensure accurate implementation.
  • Reasoned Pushback: Provide technical justifications when disagreeing with feedback.
  • Use Case: When a reviewer suggests a change, this skill will first analyze if the suggestion is technically sound, if it breaks existing functionality, or if it aligns with the project's goals, before proceeding with implementation.

Quick Start

Use the receiving-code-review skill to evaluate feedback from an external reviewer.

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 against my existing codebase?▼

Handling code review feedback involves applying technical rigor to evaluate suggestions, requesting clarification for ambiguous comments, and providing reasoned pushback with technical justifications when disagreeing with the reviewer.

When should I pushback on code review suggestions?▼

You should pushback on code review suggestions when feedback violates architectural decisions or YAGNI principles. Providing reasoned pushback with technical justifications ensures that only technically sound and necessary changes are implemented.

How do I prioritize code review feedback by issue severity?▼

Prioritizing code review feedback by issue severity requires categorizing comments by type and impact. This approach helps manage implementation based on the severity of the issue, ensuring critical technical corrections are addressed first.

What is the best way to request clarification for ambiguous code review comments?▼

The best way to handle ambiguous code review comments is to request clarification directly. This ensures accurate implementation by resolving uncertainty before modifying the codebase, preventing incorrect or unnecessary changes.

Does evaluating code review feedback require adherence to YAGNI principles?▼

Yes, evaluating code review feedback requires adherence to YAGNI principles to prevent implementing unnecessary features. This ensures that accepted changes align strictly with project-specific architectural decisions and current requirements.

Related Skills

Explore More Software Engineering Skills→
JhabbigJhabbig

receiving-code-review

Verify code review feedback against the codebase before implementation.

Community
Intermediate
ather-techieather-techie
6

commit-message

Generate standardized git commit messages from staged changes and repository history.

Community
Intermediate
hmpshmps

receiving-code-review

Validate code-review feedback for technical correctness before implementation.

Community
Intermediate
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced