菜单
This skill should be used when the user asks for a "GPT second opinion", wants a "cross-model review", needs to "check a plan before committing", wants another view after repeated failures, or explicitly invokes "codex-advisor".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/fcakyon/claude-codex-settings --skill codex-advisor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.
This skill should be used when writing or revising text, including responses, documentation, comments, emails, posts, reports, and messages, especially when the user asks to "humanize", "write naturally", "remove AI tone", or "avoid AI writing".
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
正在显示 SKILL.md
基于 SOC 职业分类
| name | codex-advisor |
| description | This skill should be used when the user asks for a "GPT second opinion", wants a "cross-model review", needs to "check a plan before committing", wants another view after repeated failures, or explicitly invokes "codex-advisor". |
Get a focused second opinion from GPT through the Codex CLI, without handing the work over to it.
In Claude Code, delegate to the native codex-advisor agent. It receives the
recent conversation automatically, so do not paste the history yourself.
Elsewhere, run this exact shape from this skill's directory so the request reaches standard input:
node scripts/ask_codex.mjs <<'REVIEW'
the review request
REVIEW
State the decision, the evidence behind it, and any constraint that changes the verdict. Name the paths that matter: the reviewer has read-only access and checks load-bearing claims itself.
Return the answer without rewriting it. If codex is missing or unauthenticated,
surface the error and ask the user to install it or sign in. Never review in its
place.
Pinned to gpt-5.6-sol at medium reasoning effort. Inside Codex that may be the
model already doing the work, so set CODEX_ADVISOR_MODEL to a different one.
Give the verdict serious weight. If a step it recommends fails when tried, or a file contradicts a specific claim, surface the conflict instead of following the review blindly.