codex result handling

Internal guidance for presenting Codex helper output back to the user

GitHub

githubcommunityclaudecodex

0.0

0 installs33.6K GitHub starsby openai

Skill Introduction

Overview

Internal guidance for presenting Codex helper output back to the user

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, claude, codex work faster.

Developers, testers, and maintainers who handle Development tasks in Focus Code.
Teams that already trust workflows or content from openai.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Tasks related to github, community, claude, codex that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Structured around Development, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, claude, codex, so it can be filtered by concrete task intent.

Install

Copy Install Command

focus install codex-result-handling-10b68d

Primary filemarkdown2 KB

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.

Overall rating

0.0

0 comments

No reviews yet