Codex Stage 1 execute skill. Run the execution + quality polish + delivery stages of review-loop against one of three entry modes: resume an approved session (--session), execute a user-supplied plan (--plan), or run a pure-CR pass on the current working tree (--review-only). Supports batched runs via --stop-after .…
Codex Stage 1 planning-only skill. Drives a work item from raw description to a reviewer-approved plan in .review-loop/sessions/{uuid}.md, then exits with a hint to resume via review-loop:execute --session . Use when you want plan-only iteration without immediately entering execution.
Codex-native Stage 1 review-loop skill. Orchestrates planning and execution with a Codex Executor and Claude/Codex reviewer backends while sharing the .review-loop protocol with Claude Code.
Instructions for NYTC69/review-loop, covering review-loop — development notes, known pitfalls, plugin agent type sandbox bug (critical), readme.md must stay intact (lint ssot dependency) and plugin cache & version bump.
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best…
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes after generating large documentation comments, before finalizing code that adds or modifies comments, when reviewing existing comments for potential technical debt or comment rot, and when…
The Executor agent in a review-loop workflow. Use this agent when the Orchestrator needs to produce a solution plan for a work item, refine a plan based on reviewer feedback, or implement an approved plan with actual code changes. This agent does the planning and coding work.
Use this agent when you need to review code for test coverage quality and completeness. This agent should be invoked after code is written or updated to ensure tests adequately cover new functionality and edge cases.
The Reviewer agent in a review-loop workflow. Use this agent when the Orchestrator needs an independent critical review of a solution plan or a set of code changes produced by the Executor. This agent reads and analyzes but never modifies files. Returns a structured verdict.
Use this agent when reviewing code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoked proactively after completing work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors.
Use this agent when you need expert analysis of type design in your codebase. Specifically use it when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, during code review to check all types being added, or when refactoring existing types to improve their design…
Iterative review-fix loop: reviews code, auto-fixes issues, repeats until clean or stuck. Finishes with reorganize (for large changes), simplify + test consolidation.
Comprehensive code review using specialized agents. Each agent focuses on a different quality aspect (code, errors, comments, types, tests, simplify). Runs sequentially by default or in parallel on request.