back
loading skill details...
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses…
AI-powered code analysis, refactoring, and automated editing via Codex CLI with GPT-5.2. Runs codex exec and codex resume commands with configurable reasoning effort (xhigh, high, medium, low) and sandbox modes (read-only, workspace-write, danger-full-access) Defaults to GPT-5.2 model (76.3% SWE-bench performance); supports gpt-5.2-max, gpt-5.2-mini, and gpt-5.1-thinking for different complexity and cost trade-offs Session continuity: resume prior Codex work at any time using codex resume --last without repeating configuration flags Suppresses thinking tokens by default; ask to see stderr for debugging or explicit reasoning inspection Codex Skill Guide Running a Task Default to gpt-5.2 model. Ask the user (via AskUserQuestion) which reasoning effort to use (xhigh,high, medium, or low). User can override model if needed (see Model Options below). Select the sandbox mode required for the task; default to --sandbox read-only unless edits or network access are necessary. Assemble the command with the appropriate options: -m, --model <MODEL> --config model_reasoning_effort="<high|medium|low>" --sandbox <read-only|workspace-write|danger-full-access> --full-auto -C, --cd <DIR> --skip-git-repo-check Always use --skip-git-repo-check. When continuing a previous session, use codex exec --skip-git-repo-check resume --last via stdin. When resuming don't use any configuration flags unless explicitly requested by the user e.g. if he species the model or the reasoning effort when requesting to resume a session. Resume syntax: echo "your prompt here" | codex exec --skip-git-repo-check resume --last 2>/dev/null. All flags have to be inserted between exec and resume. IMPORTANT: By default, append 2>/dev/null to all codex exec commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests to see thinking tokens or if debugging is needed. Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user. After Codex completes, inform the user: "You can resume this Codex session at any time by saying 'codex resume' or asking me to continue with additional analysis or changes."
don't have the plugin yet? install it then click "run inline in claude" again.