review

Automate code review against STANDARDS.md and rerun project commands.

85|9|Updated May 28, 2026
One-click install
npx skills add https://github.com/ryanczak/rexyMCP --skill review-ryanczak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ryanczak/rexyMCP/tree/main/plugin/skills/review
Command: npx skills add https://github.com/ryanczak/rexyMCP --skill review-ryanczak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The review Skill addresses the challenge of manual code review processes by automating the review, rerun, and approval or bug reporting of completed phases in a software development lifecycle.

Core Features & Use Cases

  • Automated Review Process: Automates the review of code against predefined standards and acceptance criteria.
  • Rerun Commands: Re-runs project commands to ensure code quality.
  • Approve/Report Bugs: Approves phases as complete or reports bugs for further investigation.
  • Use Case: For a software development team, this Skill can automatically verify the completion of a development phase and ensure it meets all required standards before marking it as done.

Quick Start

Run the review skill on a completed phase using the command: 'review <phase>' where <phase> is the identifier of the phase to be reviewed.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review processes for milestone-based development?

Automated code review verifies completed development phases against standards defined in STANDARDS.md. It reruns project commands to ensure quality, then either approves the phase as complete or reports bugs for further investigation.

How does automated verification work when reviewing code against predefined standards?

Automated verification works by rerunning project commands and checking the completed code against acceptance criteria defined in STANDARDS.md. It validates the source code quality and automatically flags any deviations or bugs found during the review cycle.

What do I need to set up before running an automated code review on my project?

You need to provide access to the project source code, define project commands for reruns, and create a STANDARDS.md file containing the acceptance criteria. The development workflow must be milestone-based with identifiable phases to run the review.

Can I use this automated review for milestone-based software development workflows?

Yes, this automated review is applicable to milestone-based development workflows. It requires access to the project source code and defined commands to verify completed phases against predefined standards before marking them as done.

What happens when a code review identifies bugs during the verification process?

When the review identifies bugs during verification, it reports them for further investigation instead of approving the phase. This prevents the completed development phase from being marked as done until the code meets all required standards.