aped-receive-review

Convert code review comments into verified, item-by-item implementation decisions.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-receive-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-receive-review
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-receive-review
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-receive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents rushed, emotional, or incorrect implementation of code review feedback by enforcing technical verification before changes.

Core Features & Use Cases

  • Evidence-first response: Restates each feedback item, verifies it against the codebase, and only then responds.
  • YAGNI usage gating: When reviewers ask for “proper” implementation, it confirms the feature is actually used before extending it.
  • Multi-item clarification gate: Clarifies unclear items first to avoid partial or conflicting fixes.
  • Validation-driven implementation: Implements one item at a time with testing and no regressions before moving on.
  • Artefact handoff integration: Writes and routes review-response work through APED’s configured ticket/PR workflow.

Quick Start

Use the aped-receive-review skill when you paste review comments that you need to address, or when aped-dev returns review findings to re-implement, then follow its steps to verify each item against the repository before changing code.

Frequently Asked Questions about aped-receive-review

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

FAQPage Schema
How do I handle code review feedback without making rushed or incorrect code changes?

Handling code review feedback safely requires restating each comment, verifying the issue against the codebase, and implementing fixes one item at a time with tests to prevent regressions. This approach enforces evidence-first implementation before changing any code.

What is YAGNI usage gating when responding to GitHub PR review comments?

YAGNI usage gating verifies whether a requested feature is actually used in the codebase before extending its implementation. When reviewers ask for a proper implementation, this check confirms the feature is referenced, preventing unnecessary code additions.

How do I process multi-item code review feedback that contains unclear or conflicting requests?

Processing multi-item code review feedback requires clarifying unclear items first before making any fixes. This clarification gate prevents partial or conflicting implementations by ensuring every review comment is technically verified against the repository.

Can I use this code review response workflow for Slack messages and GitHub thread notes?

Yes, the code review response workflow applies to user-provided PR comments, GitHub thread review notes, Slack messages, and feedback generated by development tools. It converts these incoming messages into technically verified implementation decisions.

What is the best way to verify code review comments against a repository before modifying code?

The best way to verify code review comments is to restate each requirement, run repository checks and YAGNI usage greps when appropriate, and implement fixes one item at a time. This validation-driven approach ensures no regressions occur.

Why does my code review response workflow require restating requirements before fixing issues?

A code review response workflow requires restating requirements to enforce technical verification and prevent emotional or incorrect implementation. By reading and restating each feedback item, you ensure accurate understanding before applying any code changes.