Codex Result Handling
- 522 installs
- 31.2k repo stars
- Updated July 8, 2026
- openai/codex-plugin-cc
Internal guidance for presenting Codex helper output back to the user.
About
Internal guidance for presenting Codex helper output back to the user. 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 w
- 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 d
Codex Result Handling by the numbers
- 522 all-time installs (skills.sh)
- +19 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #1,706 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
codex-result-handling capabilities & compatibility
- Capabilities
- when the helper returns codex output: · preserve the helper's verdict, summary, findings · for review output, present findings first and ke · use the file paths and line numbers exactly as t
- Use cases
- documentation
What codex-result-handling says it does
Internal guidance for presenting Codex helper output back to the user
npx skills add https://github.com/openai/codex-plugin-cc --skill codex-result-handlingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 522 |
|---|---|
| repo stars | ★ 31.2k |
| Last updated | July 8, 2026 |
| Repository | openai/codex-plugin-cc ↗ |
How do I apply codex-result-handling using the workflow in its SKILL.md?
Internal guidance for presenting Codex helper output back to the user
Who is it for?
Developers following the codex-result-handling skill for the tasks it documents.
Skip if: Tasks outside the codex-result-handling scope described in SKILL.md.
When should I use this skill?
User mentions codex-result-handling or related triggers from the skill description.
What you get
Working codex-result-handling setup aligned with the documented patterns and constraints.
- Severity-ordered findings list
- Preserved verdict and next steps
- Labeled evidence sections
Files
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:setupand do not improvise alternate auth flows.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Pick codex-result-handling for presenting Codex helper output; use Codex execution skills to generate the underlying review content.
FAQ
What does codex-result-handling do?
Internal guidance for presenting Codex helper output back to the user
When should I use codex-result-handling?
Invoke when Internal guidance for presenting Codex helper output back to the user.
Is codex-result-handling safe to install?
Review the Security Audits panel on this page before installing in production.