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.