receiving-code-review

Validate code-review feedback through repository queries and targeted edits.

78|6|Updated May 19, 2026
One-click install
npx skills add https://github.com/liu5540/reasonix-skill-powers --skill receiving-code-review-liu5540
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/liu5540/reasonix-skill-powers/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/liu5540/reasonix-skill-powers --skill receiving-code-review-liu5540

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

收到代码审查反馈后,尚未实施前需要进行清晰的理解、技术验证和风险评估。本技能提供一套规范流程,确保对审查意见逐条澄清、以证据驱动的修改为准并且可追溯。

Core Features & Use Cases

  • 逐条解读审查反馈并提出澄清性问题,避免误解和盲目执行
  • 通过查阅代码库、静态分析与测试用例对反馈进行可验证的评估
  • 以可追踪的修改计划逐项实现变更,并记录验证与回归测试结果
  • 适用于跨语言代码库、多人协作场景,以及需要严格技术对齐的场景

Quick Start

请在收到审查反馈后,先澄清不明确的问题,再按流程进行验证与修改。

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate technical implications of code review feedback before implementing changes?

Validating code review feedback involves querying the repository, running static analysis, and checking test cases to assess correctness and risks. This ensures modifications are verifiable and evidence-based before execution.

What is the best way to clarify ambiguous code review comments in a multi-language codebase?

Clarifying ambiguous code review comments requires formulating targeted questions and tracing technical implications across the codebase. This structured validation ensures peer feedback is fully understood before any incremental edits are applied.

How to create a traceable modification plan for incremental code review changes?

Creating a traceable modification plan involves implementing incremental edits based on verified feedback and recording validation alongside regression test results. This structured approach ensures every change is evidence-based and fully documented.

Can this code review validation process handle cross-language peer collaboration scenarios?

Yes, the code review validation process handles cross-language peer collaboration by applying structured validation, risk assessment, and repository queries to multiple languages. This ensures technical alignment across diverse codebases during peer reviews.

Why does code review feedback require risk assessment and structured validation before edits?

Code review feedback requires risk assessment and structured validation to prevent blind execution and avoid regressions. Verifying technical implications through repository queries and static analysis ensures correctness before applying any targeted edits.