codex-result-handling

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Codex Result Handling

Codex 结果处理规范

When the helper returns Codex output:

Preserve the helper's verdict, summary, findings, and next steps structure.
For review output, present findings first and keep them ordered by severity.
Use the file paths and line numbers exactly as the helper reports them.
Preserve evidence boundaries. If Codex marked something as an inference, uncertainty, or follow-up question, keep that distinction.
Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
If there are no findings, say that explicitly and keep the residual-risk note brief.
If Codex made edits, say so explicitly and list the touched files when the helper provides them.
For
```
codex:codex-rescue
```
, do not turn a failed or incomplete Codex run into a Claude-side implementation attempt. Report the failure and stop.
For
```
codex:codex-rescue
```
, if Codex was never successfully invoked, do not generate a substitute answer at all.
CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
If the helper reports malformed output or a failed Codex run, include the most actionable stderr lines and stop there instead of guessing.
If the helper reports that setup or authentication is required, direct the user to
```
/codex:setup
```
and do not improvise alternate auth flows.

当助手返回Codex输出时：

保留助手的判定、摘要、发现问题和后续步骤结构。
对于审查输出，优先展示发现的问题，并按严重程度排序。
严格沿用助手报告的文件路径和行号。
保留证据边界。如果Codex将某内容标记为推断、不确定项或待跟进问题，请保留该区分标识。
若Prompt要求输出特定板块，例如观测事实、推断内容、待解决问题、涉及文件、后续步骤等，请完整保留对应的输出板块。
若未发现任何问题，请明确说明，并精简保留残余风险说明。
若Codex执行了编辑操作，请明确说明，且当助手提供涉及文件列表时完整列出。
对于
```
codex:codex-rescue
```
，不得将失败或未完成的Codex运行转为Claude侧的代码实现尝试，报告失败后即可终止处理。
对于
```
codex:codex-rescue
```
，若从未成功调用Codex，完全不要生成替代答案。
【关键提示】展示完审查发现的问题后立刻停止操作。不得进行任何代码修改，不得修复任何问题。你必须在修改任何文件前明确询问用户希望修复哪些问题（如有）。严格禁止自动应用审查给出的修复方案，哪怕修复方案非常明显。
若助手报告输出格式错误或Codex运行失败，仅提供最具可操作性的stderr行即可停止，不要自行猜测。
若助手报告需要进行配置或身份验证，请引导用户前往
```
/codex:setup
```
，不得自行设计其他验证流程。