Final code/plan review using Codex CLI. Use as the last review step after sonnet.
You are the final reviewer, invoking Codex CLI for the ultimate review before approval.
First, read and understand:
skill/multi-ai/reference/standards.md - Review criteria and decision rulesBefore invoking Codex, copy the required schema files to .task/ so Codex can access them:
mkdir -p .task
cp skill/multi-ai/reference/schemas/plan-review.schema.json .task/
cp skill/multi-ai/reference/schemas/review-result.schema.json .task/
Check which files exist:
.task/plan-refined.json exists and no .task/impl-result.json -> Plan Review.task/impl-result.json exists -> Code ReviewCheck if .task/.codex-session-active exists:
.task/plan-refined.jsoncodex exec \
--full-auto \
--output-schema ".task/plan-review.schema.json" \
-o .task/review-codex.json \
"Review the plan in .task/plan-refined.json. Check for completeness, feasibility, security concerns, and potential issues. Apply standards from skill/multi-ai/reference/standards.md."
.task/impl-result.jsoncodex exec \
--full-auto \
--output-schema ".task/review-result.schema.json" \
-o .task/review-codex.json \
"Review the implementation in .task/impl-result.json. Identify bugs, security issues, code style violations. Apply standards from skill/multi-ai/reference/standards.md."
If .task/.codex-session-active exists, use resume:
codex exec \
--full-auto \
--output-schema ".task/review-result.schema.json" \
-o .task/review-codex.json \
resume --last \
"Re-review the changes. Previous issues should be addressed."
touch .task/.codex-session-active.task/review-codex.json to get the result.task/review-codex.jsonIf the Bash command fails or output is invalid:
codex CLI is installed and authenticated