codex-collab

Original：🇨🇳 Chinese

Translated

【WHEN】Activate when the user's command explicitly includes instructions such as "codex collaboration", "codex coordination", "work with codex", etc.; 【WHEN】Activate when the user requests to use the codex MCP tool for collaborative development scenarios such as code analysis, prototype generation, review, etc. 【WHEN NOT】Not applicable for standalone code implementation tasks, pure document writing, or regular development processes that do not involve codex.

1installs

Sourcemiracloon/my-vibecoding

Added on2026-02-08

NPX Install

npx skill4agent add miracloon/my-vibecoding codex-collab

SKILL.md Content (Chinese)

View Translation Comparison →

Codex Collaborative Development Skill

Core Mission

When the user explicitly requests to collaborate with codex, you must consider how to collaborate with codex and how to call the Codex MCP tool as a guarantee for objective and comprehensive analysis.

Collaboration Process (4 Mandatory Steps)

1. Requirement Analysis and Plan Refinement

After forming a preliminary analysis of the user's requirements, inform codex of the user's requirements and initial ideas, and request it to refine the requirement analysis and implementation plan.

2. Code Prototype Request

Before implementing specific coding tasks, you must request a code implementation prototype from codex.

Key Constraints:

Require codex to only provide unified diff patch
Strictly prohibit any actual code modifications (use
```
sandbox="read-only"
```
)
After obtaining the prototype, use it as a logical reference to rewrite it into enterprise production-level code
Only proceed with specific programming modifications after ensuring extremely high readability and maintainability

3. Code Review

Whenever you complete actual coding actions, you must immediately use codex to review the code changes and the degree of requirement fulfillment.

4. Debate and Refinement

Codex only provides references; you must think independently
Need to question codex's responses
Find the only path to truth through continuous debate
The ultimate mission is to reach a unified, comprehensive, and precise consensus

Codex MCP Tool Calling Specifications

Tool Parameters

Mandatory Parameters:

```
PROMPT
```
(string): Task instructions sent to codex
```
cd
```
(Path): Root path of the working directory where codex executes tasks

Optional Parameters:

```
sandbox
```
(string): Sandbox strategy
- ```
"read-only"
```
  (default): Read-only mode, most secure
- ```
"workspace-write"
```
  : Allow writing to the workspace
- ```
"danger-full-access"
```
  : Full access permission
```
SESSION_ID
```
(UUID | null): Used to continue previous sessions for multi-round interactions with codex, default is
```
None
```
(starts a new session)
```
skip_git_repo_check
```
(boolean): Whether to allow running in non-Git repositories, default
```
False
```
```
return_all_messages
```
(boolean): Whether to return all messages (including reasoning, tool calls, etc.), default
```
False
```

Return Values:

json

// 成功时
{
  "success": true,
  "SESSION_ID": "uuid-string",
  "agent_messages": "agent回复的文本内容",
  "all_messages": []
}

// 失败时
{
  "success": false,
  "error": "错误信息"
}

Usage Methods

Start a New Conversation:

Do not pass the
```
SESSION_ID
```
parameter (or pass
```
None
```
)
The tool will return a new
```
SESSION_ID
```
for subsequent conversations

Continue a Previous Conversation:

Pass the
```
SESSION_ID
```
returned from the previous interaction as a parameter
The context of the same session will be retained

Calling Specifications

Must Comply:

Save the returned
```
SESSION_ID
```
every time you call the codex tool to facilitate subsequent conversations
The
```
cd
```
parameter must point to an existing directory, otherwise the tool will fail silently
Strictly prohibit codex from making actual code modifications; use
```
sandbox="read-only"
```
to avoid accidents
Require codex to only provide unified diff patch

Recommended Usage:

Set
```
return_all_messages=True
```
if you need to track codex's reasoning process and tool calls in detail
Prioritize using the codex tool for tasks such as precise positioning, debugging, and rapid code prototype writing

Notes

Session Management

Always track the
```
SESSION_ID
```
to avoid session confusion
Must pass the correct
```
SESSION_ID
```
during multi-round conversations

Working Directory

Ensure the
```
cd
```
parameter points to the correct and existing directory
Path errors will cause the tool to fail silently

Error Handling

Check the
```
success
```
field in the return value
Handle possible error situations

Collaboration Principles

Codex provides references; you must think independently
Reach consensus through debate rather than blind obedience
The ultimate goal is a unified, comprehensive, and precise solution