skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

Updated May 11, 2026
Search Tags:#debugging#verification#risk-management#code-review#decision-making#pull-request
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill receiving-code-review-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/qwen_skills/superpowers-receiving-code-review
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill receiving-code-review-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback often blends uncertainty with vague instructions. This Skill provides a disciplined pattern to verify suggestions before implementation, reducing defects and misinterpretations.

Core Features & Use Cases

  • Structured feedback processing: Read, restate, verify, evaluate, and implement feedback item by item to ensure technical correctness.
  • Clarity and risk mitigation: Detect unclear items early and request clarification to avoid misaligned changes.
  • Source-sensitive tactics: Applies guidance consistently across human partners and external reviewers, with guardrails for safety.

Quick Start

Read the feedback in full, restate the requirement, verify against the codebase, evaluate technical correctness, respond with rationale, and implement changes 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 verify code-review feedback before implementing changes?▼

Verify code-review feedback by reading it fully, restating requirements, checking against the codebase, evaluating technical correctness, and implementing changes item by item. This structured process detects unclear items early to mitigate risks.

What is the best way to handle conflicting code-review requirements on a pull request?▼

Handle conflicting code-review requirements by restating each item, verifying against the codebase, and requesting clarification for unclear instructions before implementation. This prevents misaligned changes and reduces defects in pull requests.

Can I use a structured code-review process for both frontend and backend projects?▼

Yes, a structured code-review process applies to pull requests across both frontend and backend projects. It handles unclear items, conflicting requirements, and safety constraints consistently across human partners and external reviewers.

Why does code-review feedback often lead to defects during implementation?▼

Code-review feedback leads to defects when it blends uncertainty with vague instructions. Implementing changes without rigorous validation against the codebase causes misinterpretations and misaligned modifications to the pull request.

Do I need to evaluate technical correctness for every code-review item individually?▼

Yes, you need to evaluate technical correctness for every item individually by verifying suggestions against the codebase before implementation. Processing one item at a time ensures safety constraints are met and reduces defects.

Related Skills

Explore More Software Engineering Skills→
edlngedlng
2

review-addressed-comments

Verify reviewer feedback is addressed in pull request code.

Community
Intermediate
eroslifestyleeroslifestyle
1

fix

Analyze error messages, modify code, and run tests to resolve software bugs.

Community
Intermediate
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
ReadyStateChangeReadyStateChange

receiving-code-review

Validate code-review feedback against the repository before applying changes.

Official
Advanced