skills.rest
Alanlee0323
Alanlee0323COMMUNITY
Explore all skills by this author →
GitHub

handling-review

Verify code review feedback against repository state before implementing changes.

Updated Jan 20, 2026
Search Tags:#anti-patterns#communication#verification#safety#code-review#engineering-rigor
One-click install
npx skills add https://github.com/Alanlee0323/my-agent-skills --skill handling-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handling-review
Source: https://github.com/Alanlee0323/my-agent-skills/tree/main/handling-review
Command: npx skills add https://github.com/Alanlee0323/my-agent-skills --skill handling-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps prevent performative agreement and unverified changes by ensuring feedback is carefully evaluated, understood, and technically validated before implementation.

Core Features & Use Cases

  • Verify before implementing changes to ensure technical correctness.
  • Ask clarifying questions when feedback is unclear to avoid misinterpretation.
  • Protect users by prioritizing technical soundness over social comfort and by gatekeeping destructive or anti-pattern changes.

Quick Start

Provide the code review feedback and the current code context, and ask me to verify before implementing changes.

Frequently Asked Questions about handling-review

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

FAQPage Schema
How do I prevent performative agreement when processing code review feedback?▼

To prevent performative agreement during code review, implement a disciplined workflow that reads feedback, asks clarifying questions, verifies suggestions against the repository state, and evaluates technical correctness before making any changes.

How do I handle destructive or anti-pattern requests in code reviews?▼

Handle destructive code review requests by gatekeeping those changes, prioritizing technical soundness over social comfort, and technically evaluating the feedback against repository state to block anti-pattern implementations.

What is the best way to verify code review feedback before implementing changes?▼

The best way to verify code review feedback is to check the suggestions against the current repository state, clarify any unclear items, and evaluate technical correctness to ensure feedback is fully understood before implementation.

Why should I clarify unclear code review comments before modifying code?▼

You should clarify unclear code review comments to avoid misinterpretation, prevent unverified changes, and ensure that the requested modifications maintain technical correctness and engineering rigor.

Can I use a structured workflow to evaluate external code review suggestions?▼

Yes, you can use a structured workflow to evaluate external code review suggestions by reading the feedback, verifying it against the repository state, and validating technical correctness to ensure only sound changes are implemented.

When do I need to gatekeep feedback to protect code from unverified changes?▼

You need to gatekeep feedback when facing destructive requests or anti-pattern suggestions, ensuring all feedback is technically evaluated and verified against the repository state before implementing any code modifications.

Related Skills

Explore More Software Engineering Skills→
galangryandanagalangryandana
20

receiving-code-review

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

Community
Basic
zenchantlivezenchantlive
4

receiving-code-review

Resolve ambiguous code review feedback by verifying changes before implementation.

Community
Advanced
vtgiang-dotcomvtgiang-dotcom
3

requesting-code-review

Verify staged Git changes with security scans and baseline checks before commits.

Community
Intermediate
meteoricprovidermeteoricprovider
1

evaluate-ai-review-comments

Verify AI-generated pull request review comments for factual accuracy and contract alignment.

Community
Advanced