菜单
Use when the user wants to defer a codex-pair HIGH finding so the Stop-gate stops blocking turn-end. Records an acknowledgement in .codex-pair/state/acks.json keyed by the 16-char hash printed in the gate's block message. Usage /codex-pair-ack <hash> "<reason>".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | codex-pair-ack |
| description | Use when the user wants to defer a codex-pair HIGH finding so the Stop-gate stops blocking turn-end. Records an acknowledgement in .codex-pair/state/acks.json keyed by the 16-char hash printed in the gate's block message. Usage /codex-pair-ack <hash> "<reason>". |
| user_invocable | true |
Records an ack for the given finding hash so the codex-pair Stop-gate skips it on future turn-ends. The gate prints a full 16-char hash in its block message, e.g. [fc69d46835dfd2ab] src/auth.ts — pass that hash verbatim.
Parse args. The first whitespace-delimited token is <hash> (16-char hex). The remaining text (strip enclosing quotes if present) is <reason>. If either is missing, print usage and stop:
Usage: /codex-pair-ack <hash> "<reason>"
Example: /codex-pair-ack fc69d46835dfd2ab "false positive — test-only code path"
Locate the .codex-pair/ directory. Walk up from the current working directory looking for .codex-pair/context.md. The directory that contains .codex-pair/ is <markerDir>. If no marker is found after reaching the filesystem root, tell the user:
codex-pair is not enabled in this project (no .codex-pair/context.md found). Nothing to acknowledge.
Validate the hash before using it: it must match ^[0-9a-f]{16}$. If it does not, print the usage block from step 1 and stop (a malformed hash means the user mistyped it).
Record the ack by running the Bash command below. Substitute real values for <plugin-root> (the absolute path of this plugin, i.e. the value of CLAUDE_PLUGIN_ROOT), <markerDir>, and <hash>. Do NOT interpolate <reason> into the command string — the reason is read from stdin via a single-quoted heredoc so the shell never expands $(...), backticks, or quotes inside it (injection-safe). Replace the <reason> line with the user's reason text verbatim:
node --input-type=module -e '
import { addAck } from "<plugin-root>/scripts/lib/state.mjs";
import { readFileSync } from "node:fs";
// With `node -e CODE A B`, process.argv = [node, A, B] (no script-file
// placeholder), so argv[1]=markerDir, argv[2]=hash.
addAck(process.argv[1], process.argv[2], { reason: readFileSync(0, "utf8").trim() });
' "<markerDir>" "<hash>" <<'CODEX_PAIR_ACK_REASON'
<reason>
CODEX_PAIR_ACK_REASON
addAck writes to <markerDir>/.codex-pair/state/acks.json (creating the directory if needed). The hash is passed verbatim — no resolution is performed.
Confirm to the user:
Acknowledged `<hash>` — <reason>. The Stop-gate will skip this finding.
If the node one-liner exits non-zero, surface the error output so the user can diagnose it.
Review the current code changes specifically with OpenAI GPT-5.6 Sol. Use when the user asks for a Sol review, says "review with Sol", wants a model-pinned Codex review, or invokes /sol-review.
Generate an image via OpenAI's gpt-image-2 model through the Codex CLI. Use when user asks to "generate an image", "create an image", "make a picture of", "render a graphic", "draw something", or wants visual content via Codex. Requires codex-cli >= 0.125.0 with the `image_generation` feature flag enabled (stable + on-by-default since 0.125).
This skill should be used when the user asks to "compare LLMs", "see how each provider answers", "side-by-side response", "what do Gemini, Codex, Ollama, and Antigravity think", or wants raw responses from multiple providers without synthesis. Unlike /brainstorm (which synthesizes findings) or /multi-review (which validates code reviews), /compare just shows each provider's answer side-by-side.
Get a second opinion from Google Antigravity (agy) on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. Use when the user asks to "review with Antigravity", "Antigravity code review", or "ask agy to check my code".
Show codex-pair status and set up the per-edit Codex review hook for this project. Detects whether codex-pair is active, paused, or not yet configured. On first run (no marker), offers interactive setup with auto-detected project context. On subsequent runs, shows current state, recent review activity, and toggle instructions. The per-edit hook itself runs automatically; this command is the human-facing dashboard for it.
Request a review of the current code changes from the Fable model. Use when the user asks for a Fable review, says "review with Fable", wants Fable's independent perspective on a diff, or invokes /fable-review.