codex-collaborator

Guide Codex MCP workflows through requirements analysis, prototype retrieval, and code review.

1|1|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/tianguzhe/zsh-config --skill codex-collaborator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-collaborator
Source: https://github.com/tianguzhe/zsh-config/tree/main/claude/skills/codex-collaborator
Command: npx skills add https://github.com/tianguzhe/zsh-config --skill codex-collaborator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines Codex MCP collaboration across feature development, refactoring, and complex logic by enforcing a three-stage workflow: requirements analysis, prototype retrieval, and code review, while ensuring read-only safety and critical questioning.

Core Features & Use Cases

  • Three-stage collaboration: requirements analysis → prototype retrieval → code review to ensure thorough planning and validation.
  • Read-only safety: all Codex interactions run in a read-only sandbox with session ID reuse to preserve context and prevent unintended modifications.
  • Structured prompts: guided prompts ensure precise analysis, safe prototyping, and rigorous code review with explicit risk checks.
  • Use Case: When initiating a new feature or major refactor, trigger Codex Collaborator to clarify requirements, generate a read-only prototype patch, and conduct a formal review before merging.

Quick Start

Start a Codex Collaborator session by providing a project path and a high-level user need. Then, execute Phase 1 to analyze requirements, Phase 2 to retrieve a read-only prototype patch, and Phase 3 to perform a formal code review.

Frequently Asked Questions about codex-collaborator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce read-only safety during Codex MCP code collaboration?

Read-only safety during Codex MCP collaboration is enforced by running all interactions in a read-only sandbox with session ID reuse, preventing unintended modifications while preserving context for analysis, prototyping, and review.

What is the best way to structure Codex MCP workflows for new feature development?

The best way to structure Codex MCP workflows is a three-stage collaboration: requirements analysis, prototype retrieval, and code review, ensuring thorough planning and validation for new features, refactors, and complex logic.

How do I start a Codex MCP collaboration session for refactoring complex logic?

Start a Codex MCP collaboration session by providing a project path and a high-level user need, then execute Phase 1 for requirements analysis, Phase 2 for prototype retrieval, and Phase 3 for formal code review.

Can I generate a prototype patch without applying changes to my codebase?

You can generate a read-only prototype patch without applying changes by using the Phase 2 retrieval process, which safely validates patches within a sandbox environment using session ID reuse to preserve context.

Does Codex MCP collaboration support formal code review with risk checks?

Codex MCP collaboration supports formal code review with explicit risk checks through structured prompts, guiding rigorous analysis and validating prototype patches before merging any changes.