Results for “codex”

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

The English summary is being prepared. Showing the original description.

Runs a single Codex (ChatGPT/OpenAI) review check-fix cycle on a PR using gh CLI. Use this skill whenever the user wants to: check and fix Codex review comments, request a Codex code review on a PR, or iterate on PR feedback from the chatgpt-codex-connector bot. Trigger on phrases like 'codex review', '@codex review', 'fix codex comments', 'iterate on PR', 're-review with codex', or when the user mentions 'gh pr' with 'codex'. Combine with /loop for automated repeated cycles, e.g. '/loop 2m /codex-review'.

The English summary is being prepared. Showing the original description.

調査(read-only)または雑務(workspace-write)をCodexへ委譲し、結論をJSONで受け取る。Triggers on: '/codex-task', 'Codexで調べて', 'Codexにやらせて', 'Codexへ委譲'

The English summary is being prepared. Showing the original description.

Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.

• Starting a Claude Code session in a thread
• Continuing work with an external coding agent
• Relaying prompts directly through acpx

Create or update Codex skills that capture task-specific guidance. Organize instructions in SKILL.md, add useful scripts, references, or assets when needed, and validate the structure while keeping the skill focused on its intended work.

• Turn a recurring workflow into a Codex skill
• Refine instructions in an existing skill
• Organize reference documents and helper scripts

Use Codex to manage Odysseus todos, calendars, memory, and documents, and read or draft email. Through its permission-scoped API, the skill also supports reminders and launching, inspecting, or stopping Cookbook model servers.

• Create a timed reminder as a todo
• Check calendar events and add appointments
• Read email and prepare an editable reply draft

Launch the example Remotion Studio locally and open it in Codex’s built-in browser. The workflow installs dependencies, builds the monorepo, and uses the URL reported by Studio to reach the correct running instance.

• Launching the example Remotion Studio
• Opening the local Studio interface in Codex
• Finding the correct Studio URL across working copies

Launch the Remotion documentation site locally and open it in the Codex in-app browser. The workflow installs dependencies, builds the project, starts Docusaurus, and reports the actual preview URL and server status.

• Launch the local Remotion documentation site
• Preview documentation changes in Docusaurus
• Open the documentation preview inside Codex

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

Create a local Codex plugin scaffold with its required configuration file and optional folders. Generate or update marketplace entries to define display order, installation availability, and authentication timing before testing or publishing.

• Start a new local Codex plugin
• Add optional folders to a plugin
• Register a plugin in a local marketplace

Move supported Claude Code instructions, skills, agents, and MCP tool connection settings into Codex. The workflow inspects sources, previews changes, validates converted files, and reports items that need manual setup or review.

• Move project instructions and skills to Codex
• Convert slash commands into Codex skills
• Migrate agents, MCP connections, and supported hooks

Create animated Codex pets from character art, text ideas, or brand cues. Generate nine animation states, assemble a transparent sprite sheet, check appearance and movement, and package the results with a pet configuration file.

• Turn character art into an animated Codex pet
• Create a pet in plush, clay, or other non-pixel styles
• Design a mascot from company or brand cues

Switch PUA's narration to an encouragement-first style in Codex CLI through the equivalent of Claude Code's /pua:yes command. The skill preserves verification requirements and requires command or output evidence before reporting completion.

• Calling the equivalent of /pua:yes from Codex CLI
• Switching task narration to an encouraging style
• Keeping verification requirements while changing narration

Switch PUA to offline mode from Codex CLI. This alias updates the offline setting and sets feedback frequency to zero while preserving other configuration fields, then reports the mode change.

• Switching PUA to offline mode
• Setting feedback frequency to zero
• Calling the offline command from Codex CLI

Put Codex CLI in a technical lead role that writes task prompts and manages P8 execution through the p9 protocol. The agent stays focused on coordination and only implements code when explicitly reassigned.

• Assign a technical lead role in Codex CLI
• Write task prompts for P8 execution
• Keep coordination separate from code implementation

Provides a Codex CLI alias for loading the mama coaching protocol. It switches visible narration to Chinese-mother nagging while retaining verification rules, and preserves unrelated configuration fields whenever it updates the PUA settings file.

• Loading mama mode from Codex CLI
• Changing narration while retaining verification rules
• Preserving unrelated settings when updating the configuration

Access the equivalent of Claude Code's /pua:pro command from Codex CLI. The alias invokes the pro protocol for self-improvement, KPI performance measures, and configuration commands, with all processing kept local.

• Calling the equivalent of /pua:pro from Codex CLI
• Using the pro protocol for self-improvement and KPI commands
• Managing PUA settings locally

Use past local Codex sessions to propose updates to a selected skill and project memory file. Recurring tasks are replayed, changes are checked on separate validation tasks, and proposals are staged for review before adoption.

• Turn recurring Codex requests into skill updates
• Consolidate feedback into skills and project memory
• Compare validation scores before applying changes

Check whether Codex is using Weave Router or its default provider. This skill runs a status command and summarizes the result in one line without changing any configuration.

• Checking whether Codex uses Weave Router
• Checking whether the default provider is active
• Reviewing routing status without changing settings

Pin the current Codex session to a chosen model through Weave Router. This short alias accepts a model ID, runs the included script, and reports the router’s response while allowing the current turn to continue.

• Pinning a Codex session to a chosen model
• Using a short alias for force-model
• Checking the router’s response after pinning a model

Diagnose Codex behavior within BB, including question cards, MCP requests for user input or approval, Computer Use app access, model availability, service tiers, session options, and persistent goals, using thread and provider controls.

• Investigate a Codex turn waiting for an answer
• Review app access and MCP tool approvals
• Check models and service tiers on the execution host

SUPERSEDED by /claudex-loop (formerly /crucible; adds a Phase 0 research/recon pass + rebuilt interview) — prefer that skill unless you explicitly want this one. Two-act plan hardening. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan or design, one question at a time, recommending an answer for each and exploring the codebase when it can answer itself, until every branch of the decision tree is resolved. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-me-codex", "grill me then have codex review", "grill me and stress-test the plan", "interview me about this plan then get a second model on it", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants both alignment AND a cross-model sanity check before implementation. Builds on Matt Pocock's grill-me (MIT). For the docs-aware variant use /grill-with-docs-codex; if you already have a plan and want only the Codex review use /codex-review. NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.

The English summary is being prepared. Showing the original description.

Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" — or to run a queue of coding tasks through Codex while staying the reviewer. Prefer it over a one-shot Codex forwarder (such as the codex-rescue agent) when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

The English summary is being prepared. Showing the original description.

Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit. Two explicit subcommands. `review` (also the bare/back-compat default) — codex (reviewer) critiques the current diff and a Claude subagent (author) fixes/disputes, looping until they agree. `answer` — Claude and codex each answer a freeform prompt in parallel, then cross-check until they agree, and a unified answer is returned. Use when the user types `/codex-debate`, asks to "have codex review this", "run the codex debate", "review this PR with codex", "argue this with codex until you agree", or passes a question to "have Claude and codex debate/answer until they agree".

The English summary is being prepared. Showing the original description.