codex-cli
Operate OpenAI Codex CLI (terminal coding agent) to accomplish software engineering tasks. Use when the user asks to: run codex commands, use codex for coding tasks, execute codex exec for automation, do code review with codex, manage codex sessions (resume/fork), configure codex (config.toml, approval modes, sandbox), use codex cloud, set up MCP servers in codex, or any task involving the `codex` command-line tool. Triggers: codex, codex exec, codex review, codex cloud, codex mcp, codex resume, codex sandbox, openai codex.
What this skill does
# Codex CLI OpenAI's terminal coding agent. Reads, edits, and runs code locally with configurable sandbox and approval controls. Built in Rust, open source. ## Quick Reference \`\`\`bash # Interactive session codex "your prompt here" # Non-interactive (scripting/CI) codex exec "your prompt here" codex exec --json "prompt" # JSONL output codex exec -o result.txt "prompt" # Save last message # Code review codex review # Review current branch vs main codex review --uncommitted # Review all uncommitted changes codex review --base develop # Review against specific branch codex review --commit abc123 # Review a specific commit # Session management codex resume # Pick from recent sessions codex resume --last # Continue most recent codex fork --last # Fork most recent into new thread # Cloud tasks (experimental) codex cloud exec --env ENV_ID "task" codex cloud list codex cloud apply TASK_ID codex cloud diff TASK_ID \`\`\` ## Key Flags | Flag | Short | Purpose | |------|-------|---------| | \`--model\` | \`-m\` | Select model (e.g. \`gpt-5.3-codex\`, \`o3\`) | | \`--sandbox\` | \`-s\` | \`read-only\` / \`workspace-write\` / \`danger-full-access\` | | \`--ask-for-approval\` | \`-a\` | \`untrusted\` / \`on-failure\` / \`on-request\` / \`never\` | | \`--full-auto\` | | Shortcut: \`-a on-request -s workspace-write\` | | \`--image\` | \`-i\` | Attach image(s) to prompt | | \`--search\` | | Enable live web search | | \`--cd\` | \`-C\` | Set the working directory for the \`codex\` command. This directory will be used as the base for operations by subcommands like \`exec\`, \`review\`, \`cloud exec\`, etc. This flag should be passed directly to the \`codex\` command. For example: \`codex --cd /path/to/project review\`. | | \`--add-dir\` | | Grant additional writable directories | | \`--config\` | \`-c\` | Override config value (e.g. \`-c model="o3"\`) | | \`--profile\` | \`-p\` | Load named config profile | | \`--oss\` | | Use local model provider (LM Studio / Ollama) | | \`--json\` | | (exec only) JSONL output | | \`--output-last-message\` | \`-o\` | (exec only) Write last message to file | | \`--yolo\` | | Bypass all approvals and sandbox (DANGEROUS) | ## Approval Modes - **untrusted** (default): Only trusted commands (ls, cat, sed…) run without asking. Others prompt user. - **on-failure**: Run all commands freely. Only prompt if a command fails. - **on-request**: Model decides when to ask. - **never**: Never prompt. Failures go straight back to model. ## Sandbox Modes - **read-only**: No file writes, no network. - **workspace-write**: Write only in workspace + specified dirs. Configurable network access. - **danger-full-access**: Unrestricted. Use only in isolated environments. ## Slash Commands (Interactive) | Command | Purpose | |---------|---------| | \`/model\` | Switch model mid-session | | \`/permissions\` | Adjust approval/sandbox settings | | \`/review\` | Run code review | | \`/diff\` | Show git diff including untracked files | | \`/compact\` | Summarize conversation to free tokens | | \`/mention\` | Attach file to conversation | | \`/new\` | Start new conversation in same session | | \`/resume\` | Resume saved conversation | | \`/fork\` | Fork current conversation | | \`/init\` | Generate AGENTS.md scaffold | | \`/mcp\` | List MCP tools | | \`/status\` | Show session config and token usage | | \`/ps\` | Show background terminals | | \`/quit\` | Exit | ## Common Patterns ### CI/CD Automation \`\`\`bash # Run task non-interactively with JSON output codex exec --json --full-auto "fix all lint errors" | process_results.sh # Structured output with schema codex exec --output-schema schema.json "analyze this codebase" \`\`\` ### Code Review in CI \`\`\`bash codex review --base main --title "PR #42: Add auth" \`\`\` ### Multi-Directory Projects \`\`\`bash codex --cd ./backend --add-dir ./shared "update the API" \`\`\` ### Image-Driven Development \`\`\`bash codex -i mockup.png "implement this UI exactly" \`\`\` ### Local OSS Models \`\`\`bash codex --oss --CPA ollama -m codellama "refactor this function" \`\`\` ## Configuration Config file: \`~/.codex/config.toml\` (user-level), \`.codex/config.toml\` (project-level). For full configuration reference including all keys, MCP server setup, model providers, sandbox permissions, shell environment policies, and OpenTelemetry: see [references/config-reference.md](references/config-reference.md). ## MCP Server Management \`\`\`bash codex mcp list # List configured servers codex mcp add <name> # Add MCP server codex mcp remove <name> # Remove MCP server codex mcp login <name> # Authenticate with server codex mcp logout <name> # Remove server credentials \`\`\` Configure in config.toml: \`\`\`toml [mcp_servers.my-server] command = "npx" args = ["-y", "@my/mcp-server"] enabled = true \`\`\`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.