implement-review

Automates staged-change review workflows by routing content-aware prompts to Codex.

13|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/yzhao062/agent-config --skill implement-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-review
Source: https://github.com/yzhao062/agent-config/tree/main/skills/implement-review
Command: npx skills add https://github.com/yzhao062/agent-config --skill implement-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the review loop for staged changes by routing content-type-aware prompts to Codex (terminal or IDE plugin), organizing feedback, and iterating revisions until quality gates are satisfied.

Core Features & Use Cases

  • Content-type aware reviews for code, papers, proposals, or any text-based output.
  • Dual Codex paths: terminal and IDE plugin with structured prompts and save-contracts.
  • Phase-driven review workflow including prerequisites, plan reviews, and multi-reviewer coordination, with Review-<AgentName>.md artifacts.

Quick Start

Stage your changes, run the skill, and save the Codex review prompts to a Review-<YourAgentName>.md file.

Frequently Asked Questions about implement-review

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

FAQPage Schema
How do I automate code review for staged changes using Codex?

Automate staged-change reviews by routing content-type-aware prompts to terminal Codex sessions or IDE plugins. The workflow orchestrates a review loop for code, papers, or proposals, iterating revisions until quality gates are satisfied and saving results to Review-<AgentName>.md.

Can I use this workflow to review documents other than source code?

Yes, the review workflow supports content-type aware reviews for papers, proposals, and any text-based outputs. It orchestrates feedback across Phase 0 plan reviews through Phase 2 feedback, organizing revisions for diverse document types.

How do I route review prompts to my IDE plugin instead of a terminal?

Route review prompts to an IDE plugin by configuring the dual Codex paths during setup. The workflow supports both terminal Codex sessions and IDE plugins, structuring prompts and save-contracts to integrate directly with your development environment.

What is the best way to track feedback across multiple reviewers?

Track multi-reviewer coordination by using the phase-driven review workflow that generates Review-<AgentName>.md artifacts. This save-contract workflow ensures review traceability by organizing feedback and iterating revisions until quality gates are met.

Do I need any specific dependencies to run the staged-change review loop?

No external dependencies are required. The workflow relies on SKILL.md frontmatter for discovery and optionally uses resources in scripts/, references/, or assets/ directories to extend behavior, requiring only a Codex terminal or IDE plugin to execute.

When should I not use an automated prompt-engineering review loop?

Avoid this workflow for unstaged files or non-text-based outputs. The review loop specifically targets staged changes and text-based content, orchestrating prompts for code, papers, and proposals through Phase 0 to Phase 2 feedback cycles.