Codex Result Handling

by openaidb52e28f4d9ded852ab3942cea316258ae4ef346No licenseListed Oct 9, 2026Updated Oct 9, 2026

Internal guidance for presenting Codex helper output back to the user

FeaturedInstructions onlyAI & Agents

AI-generated overview

Internal guidance for presenting Codex helper output back to the user without altering its findings.

What it does: This skill provides internal, non-user-invocable guidance for relaying Codex helper output to the user. It specifies preserving the helper's verdict, summary, findings, and next steps, ordering review findings by severity, and keeping reported file paths, line numbers, and evidence boundaries intact. It also defines how to handle failed or malformed runs, setup or authentication prompts, and edits made by Codex.
When to use it: Use it when a Codex helper returns output that must be presented to the user, especially review findings or rescue runs. It applies when the agent needs rules for reporting failures, missing setup, or edits rather than acting on the results itself.
Requirements: No scripts or special tooling; it is instructions only. It assumes a Codex helper is available and may reference a setup command for authentication.

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.

Source and attribution

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.