# Codex Result Handling

> Internal guidance for presenting Codex output back to the user after a rescue or review run

- Skill: `ray0907/codex-result-handling` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ray0907/codex-result-handling`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ray0907/codex-result-handling/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ray0907 (https://skillmd.com/u/ray0907)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ray0907/codex-result-handling

---


# Codex Result Handling

Use this skill when presenting Codex output to the user after a `codex-rescue` or review run.

## General rules

- Preserve the verdict, summary, findings, and next-steps structure from Codex output
- Use file paths and line numbers exactly as Codex reports them — do not normalize or guess
- Keep evidence boundaries intact: if Codex marked something as an inference, uncertainty, or open question, preserve that distinction
- If there are no findings, say so explicitly and keep any residual-risk note brief
- If Codex made file edits, say so and list the touched files when available
- If Codex output is malformed or the run failed, include the most actionable stderr lines and stop — do not guess at what Codex would have said

## Review output (codex review / adversarial-review)

Present findings ordered by severity. Then **stop completely**.

Do not:
- Apply any fixes
- Suggest you are about to make changes
- Silently correct issues mentioned in the review

After presenting findings, ask the user explicitly:
> "Which of these issues, if any, would you like me to address?"

Wait for their answer before touching any file. Auto-applying review findings — even obvious ones — is not allowed.

## Rescue output (codex-rescue)

- Return Codex stdout verbatim
- Do not turn a failed or incomplete Codex run into a Claude-side implementation attempt
- If Codex was never successfully invoked, do not generate a substitute answer

## Setup / auth errors

If Codex output indicates it is not installed or not authenticated, direct the user to run:

```bash
npm install -g @openai/codex   # if not installed
codex login                    # if not authenticated
```

Do not improvise alternate auth flows.