[furedea]

全 PR を Codex がレビューする共有 workflow（furedea/reusable-workflows の codex-review.yml）を ci.yml から呼び，all-green の needs に加えます．
CI がオーナーの token で @codex review を投稿し，HEAD の commit に未解決の指摘があるか，Codex が失敗するか，20 分以内に結果がないと all-green が赤になります．PR 以外のイベント，フォークからの PR，furedea-agent 以外の bot の PR では飛ばし，成功として扱います．

• codex-review / Decide whether to review と codex-review / Codex review が成功する
• all-green が green になる

出典

• 計画: ci: request Codex reviews for every pull request with the owner's token reusable-workflows#7
• 呼び出し先: furedea/reusable-workflows@9bea83d（renovate が SHA を更新する）
• シークレット CODEX_REVIEW_TOKEN は repo review-token rotate codex で登録済み

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[chatgpt-codex-connector]

To use Codex here, create an environment for this repo.

[furedea]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-06T16:42:45.114472Z	a5c076b	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

Review summary (read-only)

No blocking findings.

• codex-review calls a reusable workflow pinned to a specific commit, gets only CODEX_REVIEW_TOKEN, and sets permissions: {}. That matches the least-privilege setup of the other jobs.
• Adding it to all-green.needs is correct. Note that all-green also fails when a needed job's result is skipped. So the PR description's claim that "skipped is treated as success" depends on the called workflow always finishing as success, never as skipped, for pushes to main, fork PRs and bot PRs. The "Decide whether to review" job should ensure this. Please confirm it on the first push to main after merging.
• I could not read furedea/reusable-workflows@9bea83d from this environment. I did not check that the called workflow works with an empty GITHUB_TOKEN permission set; that rests on the description saying all API calls use the owner's token.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: a5c076b72b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".