Loading...
Loading...
Found 215 Skills
Invoke Codex as a coworker for implementation, brainstorming, specs, and reviews. Use when you want parallel thinking, cheap execution, or a second opinion. Codex tokens are cheaper than yours — delegate aggressively. Keywords: codex, delegate, implement, draft, review, brainstorm, write tests, code review, moonbridge.
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
Read Codex logs for this repo and synthesize docs in docs/.
Create GitHub issues in this repo using the Codex issue template and the gh CLI. Use when the user asks to file/open/create a GitHub issue, track work, or request a Codex implementation run via .github/ISSUE_TEMPLATE/codex-task.md.
Compare OpenAI Codex GPT-5.3 and code-searcher responses for comprehensive dual-AI code analysis. Use when you need multiple AI perspectives on code questions.
Run Codex CLI /review via tmux to review uncommitted changes. Launches Codex in isolated tmux session, sends /review command, selects option 2, captures output. Use when you want a second opinion on uncommitted code changes.
Automated code review loop with progressive reasoning levels. Runs n parallel Codex reviews (configurable via -n), Claude addresses issues, climbs from low→xhigh reasoning until fixed point (all n clean). Human approval at each iteration.
Enables Claude Code to collaborate with OpenAI Codex CLI on Windows. Use this skill when the user wants to get a second opinion from Codex, compare approaches between Claude and Codex, or leverage both AI assistants for collaborative problem-solving. This skill supports both non-interactive mode (automatic response retrieval) and interactive mode (visual pane splitting with tmux).
Get code review from Codex AI for implementation quality, bug detection, and best practices. Use when asked to review code, check for bugs, find security issues, or get feedback on implementation patterns.
Inspect and summarize local Codex/Claude session logs using the ccbox CLI (projects, sessions, history). Use when asked to list discovered projects, find sessions for the current repo/folder, print a session timeline, or produce an evidence-based “what happened” report from a session .jsonl log under CODEX_SESSIONS_DIR.
Use when wanting independent review from external models before merging, committing, or finalizing architecture or plan decisions, or when the user asks for a second opinion, codex review, or gemini review
Have Codex CLI review uncommitted code changes. Claude Code then fixes valid issues and rebuts invalid ones. Codex re-reviews. Repeat until consensus. Codex never touches code — it only reviews.