Skip to content
cccskills
FreePublished on GitHub

codex-result-handling

Present results returned by a Codex helper while preserving findings, severity, file references, and uncertainty. This internal guidance also covers reporting edited files, failed runs, and setup requirements, with user confirmation before fixing review findings.

OriginalShow the original description

Internal guidance for presenting Codex helper output back to the user

openai/codex-plugin-cc
See how to install

Good for

  • Present review findings in order of severity
  • Keep observed evidence separate from inferences
  • Report files changed by Codex
  • Explain failed runs or required setup

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Codex Result Handling

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

codex-cli-runtime

FreeSummary

Forward tasks from Claude Code's rescue subagent to Codex through a helper script. This internal skill handles model and effort options, fresh or resumed runs, and write access, then returns the helper's output unchanged.

  • Hand off diagnosis or implementation work to Codex
  • Resume a previous Codex request
  • Start a fresh Codex run
openai/codex-plugin-cc34.4KUpdated Jul 8, 2026

gpt-5-4-prompting

FreeSummary

Compose compact, structured prompts for coding, debugging, review, and research with Codex or GPT-5.4. This internal skill defines task scope, completion criteria, output format, verification steps, and evidence requirements using consistent XML tags.

  • Define implementation scope and completion criteria
  • Include verification steps in debugging requests
  • Specify evidence requirements for code reviews
openai/codex-plugin-cc34.4KUpdated Jul 8, 2026

See all skills by openai

Report a problem with this skill