eo-review

Review implemented code against spec.md and change.md, generating review.md reports.

30|5|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/SimpleEve/eo-skills --skill eo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eo-review
Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-review
Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the post‑implementation code review process, ensuring code aligns with module specifications and change documentation while delivering a consistent, structured report.

Core Features & Use Cases

  • Document‑Based Review: Reads the module’s spec.md and the related change.md to assess code completeness and correctness.
  • Multi‑Dimensional Analysis: Evaluates functionality, logic, architecture, coding standards, security, performance, and optional cross‑layer consistency.
  • Structured Reporting: Produces a review.md file with P0‑P2 issue classification, acceptance‑criteria coverage, and TODO completion tables.

Quick Start

Ask eo-review to evaluate the latest change in a module and generate its review report.

Frequently Asked Questions about eo-review

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

FAQPage Schema
How do I generate a structured code review report for my module changes?

To generate a structured code review report, the Skill reads your module's spec.md and change.md to evaluate code completeness and correctness. It then outputs a review.md file containing P0-P2 issue classifications and acceptance-criteria coverage tables.

What is the process for verifying implemented code against module specifications?

Verifying implemented code against module specifications involves assessing functionality, logic, architecture, and security. This Skill automates that document-based review by cross-referencing your code with spec.md and change.md to produce a structured review.md report.

How do I classify code review issues by severity after implementing a change?

Classifying code review issues by severity is handled automatically by generating a review.md report. The report categorizes identified issues into P0, P1, and P2 classifications based on multi-dimensional analysis of the implemented changes.

Can I use this code review tool for modules without change documentation?

No, this code review tool requires the presence of both spec.md and change.md files within the eo-doc/dev modules. It relies on this documentation to assess code completeness and generate the structured review report accurately.

Does the code review report include a status for acceptance criteria and TODOs?

Yes, the generated code review report includes acceptance-criteria coverage tables and TODO completion status. It evaluates the implemented changes against the module specifications to ensure all documented requirements and tasks are fulfilled.

What dimensions does the automated code review analyze?

The automated code review analyzes functionality, logic, architecture, coding standards, security, performance, and optional cross-layer consistency. It uses these dimensions to identify issues and populate the structured review.md report.