ia-receiving-code-review

Verify PR and MR review feedback for correctness before implementing code changes.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-receiving-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia-receiving-code-review
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-receiving-code-review
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents AI coding agents from blindly accepting PR/MR review feedback by enforcing verification, evidence-based responses, and safe implementation ordering.

Core Features & Use Cases

  • Critical verification before action: checks whether suggestions are technically correct for the specific codebase and context.
  • Evidence-based response discipline: responds by agreeing or disagreeing with concrete justification rather than performative alignment.
  • Triage-first implementation workflow: classifies feedback, clarifies unclear items, and implements fixes one at a time after verification.
  • Headless triage support: programmatic mode returns structured AUTO-FIX / AUTO-DECLINE / ESCALATE results with safety constraints.

Quick Start

Use the skill to respond to PR review comments by asking an AI agent to verify each suggestion against the repository and only implement confirmed fixes.

Frequently Asked Questions about ia-receiving-code-review

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

FAQPage Schema
How do I verify pull request review feedback before changing code?

To verify pull request review feedback before changing code, the skill checks whether reviewer suggestions are technically correct for your specific codebase and context, requiring evidence-based justification rather than blind acceptance. It clarifies ambiguous comments before implementation.

What is the best way to triage code review comments in headless mode?

The best way to triage code review comments in headless mode is using programmatic structured outputs that classify each item as AUTO-FIX, AUTO-DECLINE, or ESCALATE, applying safety constraints to manage high-risk cases without manual intervention.

Can I automate code review triage for ambiguous suggestions?

Yes, you can automate code review triage for ambiguous suggestions by classifying feedback programmatically and requiring evidence-based verification, which ensures unclear items are clarified or safely escalated rather than implemented incorrectly.

How does evidence-based code review response discipline work?

Evidence-based code review response discipline works by forcing agents to agree or disagree with reviewer comments using concrete justification tied to the repository, preventing performative alignment and ensuring only verified fixes are implemented one at a time.

When should I escalate reviewer comments instead of auto-fixing code?

You should escalate reviewer comments instead of auto-fixing code when suggestions are classified as high-risk, context-dependent, or cannot be verified for technical correctness against the specific codebase, triggering safe escalation protocols.

Does automated PR triage support implementation ordering for fixes?

Yes, automated PR triage supports implementation ordering by classifying feedback first, clarifying unclear items, and then implementing verified fixes sequentially one at a time to maintain codebase stability.