gemini-reviewlisted

# Gemini Review Use this skill when Codex needs an independent Gemini CLI review before shipping. Run: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/gemini-companion.mjs" review "$ARGUMENTS" ``` Background routing: - Foreground use runs the normal command above. - If `$ARGUMENTS` contains `--background`, first run: ```bash node "${CODEX_PLUGIN_ROOT}/scripts/gemini-companion.mjs" reserve-job review "$ARGUMENTS" ``` - Parse the returned JSON and dispatch exactly one forwarding subagent or child worker with the returned `workerCommand` JSON argv array. The child must execute that array as argv while preserving element boundaries; if forced through a shell, quote every element. - The child runs `run-reserved-job` once through `workerCommand`; it must not inspect or reinterpret the repository. - The parent returns the job id immediately and tells the user to use `gemini-result <job-id>`. Rules: - Treat the output as review findings, not implementation instructions. - Do not fix findings in the same turn unless the user explicitly asks. - Preserve Gemini's file paths, line numbers, uncertainty markers, and residual-risk notes. - If Gemini reports no findings, still report any residual risks it listed. - Use `--structured` when the user needs schema-validated review findings; malformed structured output is a failure, not approval. - Use `--background` for long reviews through the background routing contract above so Codex can continue working and retrieve results later with `gem