본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Internal guidance for presenting Codex helper output back to the user

openai/codex-plugin-cc
설치 방법 보기

이럴 때 유용합니다

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

포함된 파일(1)

  • SKILL.md1.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

codex-cli-runtime

무료

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-cc3.4만2026년 7월 8일 업데이트

gpt-5-4-prompting

무료

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-cc3.4만2026년 7월 8일 업데이트

openai의 스킬 모두 보기

이 스킬의 문제 신고