Cc codex

Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when: (1) Backend/logic implementation, (2) Algorithm design and optimization, (3) Bug analysis and debugging, (4) API/database code generation, (5) Code quality review and refactoring. Triggers: "implement algorithm", "debug", "analyze code", "backend task", "API implementation", "optimize performance", "refactor", "generate prototype", "code review". IMPORTANT: Default sandbox="read-only" (analysis/review/patch generation); use sandbox="workspace-write" only when codex must run tests/builds to verify. Always request unified diff patches only. Supports multi-turn sessions via SESSION_ID.From its SKILL.md

Install

npx -y skills add Dianel555/DSkills --skill cc-codex

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.8 KB, as published. Nobody here has run it

Quick Start

python scripts/codex_bridge.py --cd "/path/to/project" --PROMPT "Your task"

Output: JSON with success, SESSION_ID, agent_messages, stream_file (path to the raw JSONL stream persisted line-by-line), optional stderr, and optional error.

Approvals are always disabled (codex --ask-for-approval never exec ... is used automatically, except under --yolo): exec runs headless with stdin detached, so an approval prompt could never be answered.

Parameters

usage: codex_bridge.py [-h] [--PROMPT PROMPT] [--cd CD]
                       [--sandbox {read-only,workspace-write,danger-full-access}]
                       [--SESSION_ID SESSION_ID] [--skip-git-repo-check]
                       [--return-all-messages] [--image IMAGE] [--model MODEL]
                       [--yolo] [--profile PROFILE] [--stream-file STREAM_FILE]
                       [--idle-timeout IDLE_TIMEOUT] [--ignore-user-config]
                       [--dangerously-bypass-hook-trust]
                       {mcp,plugin} ...

Codex Bridge

options:
  --PROMPT PROMPT       Instruction for the task to send to codex.
  --cd CD               Set the workspace root for codex before executing the task.
  --sandbox {read-only,workspace-write,danger-full-access}
                        Sandbox policy for model-generated commands. Defaults to `read-only`.
  --SESSION_ID SESSION_ID
                        Resume the specified session of the codex.
  --skip-git-repo-check
                        Allow codex running outside a Git repository.
  --return-all-messages
                        Return all messages (reasoning, tool calls, etc.).
  --image IMAGE         Attach image files to the initial prompt.
  --model MODEL         Model for the session (only when user explicitly requests).
  --yolo                Bypass approvals/sandboxing (last resort).
  --profile PROFILE     Load `~/.codex/<name>.config.toml` profile (only when user requests).
  --stream-file STREAM_FILE
                        Persist raw JSONL stream path.
  --idle-timeout IDLE_TIMEOUT
                        Kill codex if no output for N seconds (default 600; 0 disables).
  --ignore-user-config  Do not load `$CODEX_HOME/config.toml` (auth still uses CODEX_HOME).
  --dangerously-bypass-hook-trust
                        Run Codex hooks without persisted hook trust. DANGEROUS.

subcommands:
  mcp                   Thin passthrough to `codex mcp` (list/get/add/remove/login/logout).
  plugin                Thin passthrough to `codex plugin` (add/list/remove/marketplace).

Multi-turn Sessions

Always capture SESSION_ID from the first response for follow-up:

# Initial task
python scripts/codex_bridge.py --cd "/project" --PROMPT "Analyze auth in login.py"

# Continue with SESSION_ID
python scripts/codex_bridge.py --cd "/project" --SESSION_ID "uuid-from-response" --PROMPT "Write unit tests for that"

Config Inheritance

Source	Inherited by default?
`~/.codex/config.toml`	Yes (unless `--ignore-user-config`)
Profile (`--profile`)	Only when explicitly passed
Project `.codex/` (trusted)	Yes, when Codex trusts the project
Hooks / MCP / plugins / skills / `AGENTS.md`	Yes, via Codex runtime

Management Passthrough

python scripts/codex_bridge.py mcp list
python scripts/codex_bridge.py plugin list

Common Patterns

Prototyping (read-only, request diffs):

python scripts/codex_bridge.py --cd "/project" --PROMPT "Generate unified diff to add logging"

Verification (codex must run tests/builds — read-only blocks them):

python scripts/codex_bridge.py --cd "/project" --sandbox workspace-write --PROMPT "Run pytest, fix the failure, output a unified diff patch"

Keep requesting patch text; audit afterwards with git status && git diff.

Debug with full trace:

python scripts/codex_bridge.py --cd "/project" --PROMPT "Debug this error" --return-all-messages

Headless hooks (vetted automation only):

python scripts/codex_bridge.py --cd "/project" --PROMPT "..." --dangerously-bypass-hook-trust

What ships with it: 3 files

33.7 KB alongside SKILL.md, 2 of them executable

scripts/

codex_bridge.pyruns18.5 KB

tests/

test_codex_bridge.pyruns11.8 KB

README.md3.5 KB

Gives 0 of the 12 instructions most debug triage skills give

Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06

Find root cause before attempting any fixin 134 of 1020, across 118 files
Create a failing test case before implementing a fixin 109 of 1020, across 95 files
Read error messages and stack traces completelyin 102 of 1020, across 88 files
Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
Trace data flow backward to find the sourcein 84 of 1020, across 70 files
Form a single hypothesis before testingin 78 of 1020, across 64 files
Implement only one fix at a timein 76 of 1020, across 63 files
Question the architecture if three fixes failin 73 of 1020, across 59 files
Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
Compare broken code against working examplesin 68 of 1020, across 57 files
Write a regression test before applying the fixin 62 of 1020, across 55 files

Said here and by no other author read

request unified diff patches only
capture session id for multi-turn sessions
use workspace-write sandbox for tests or builds
audit changes with git status and git diff

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.