evanflow-review

Review pull requests with structured feedback and verification steps.

417|18|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evanflow-review
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-review
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often suffer from ambiguity and inconsistent feedback. This skill provides a structured approach to requesting and processing reviews, ensuring feedback is clear and aligned with the changes.

Core Features & Use Cases

  • Structured Review Workflow: Guide for requesting feedback, framing goals, and identifying risk areas.
  • Verification-Oriented: Encourages running local checks, re-reading diffs, and confirming changes meet the plan before approval.
  • Hand-offs & Governance: Clear hand-offs for architecture or debugging issues and documented acceptance criteria.

Quick Start

Review a recent PR by outlining goals, risks, and verification steps in your request.

Frequently Asked Questions about evanflow-review

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

FAQPage Schema
How do I structure a code review to ensure actionable feedback on a pull request?▼

To perform a structured code review, outline your PR goals, identify risk areas, and define verification steps like running local quality checks and re-reading diffs. This ensures feedback is clear and aligned with the changes.

What is the best way to process feedback from reviewers on a completed pull request?▼

Processing reviewer feedback involves re-reading diffs against the original plan and surfacing open questions to guide next actions. This verification workflow ensures reviewer comments are systematically addressed before approval.

How do I enforce verification steps before approving changes in a pull request?▼

You can enforce verification by requiring local quality checks to pass, re-reading diffs against the planned changes, and documenting acceptance criteria. This structured approach guarantees work meets the plan before final approval.

How do I handle architecture or debugging issues discovered during a PR review?▼

During a PR review, handle architecture or debugging issues by creating clear hand-offs. Documenting these separately ensures proper governance and keeps the current code review focused on immediate changes.

What should be included when requesting feedback on code changes?▼

When requesting feedback on code changes, include your goals, identified risk areas, and verification steps. Framing the request with these elements provides reviewers with the context needed for a structured code review.