grokodex-reviewlisted

# Grokodex Review Read-only code review through Grokodex MCP. **Does not modify the repo.** ## When to use - User asks to review changes, PR, working tree, or "审一下" - Findings / risks only — no implementation - Not for design-challenge-only → `grokodex-critique` - Not for apply fixes → `grokodex-run` ## Tool preference 1. Always call MCP `grok_run` with **`profile: "review"`** (required). 2. Forbidden: shell/`grok` for the review task. 3. Do not call `grok_run` without `profile` for a pure review request. ## Steps 1. Determine scope: working tree (default) or user-specified base ref. 2. Collect with host tools: `git status`, staged/unstaged diff, or `git diff base...HEAD`. For large diffs, summarize and include the most critical file hunks. 3. If there is nothing to review, tell the user and **stop** (do not call MCP). 4. Build `prompt` including: scope label, collected diff/context, review axes (correctness, security, tests, edge cases, maintainability). 5. Call: ```text grok_run prompt: <assembled> profile: review # optional: cwd, model, host_thread_id, max_turns, timeout_ms ``` 6. Present `text` findings. **Do not** start editing in the same turn unless the user explicitly asks to fix — then switch to `grokodex-run` **without** profile. ## Permissions - `profile=review` forces read-only in the bridge. Do not try to pass danger-full-access to "review harder". - If envelope `permission.notes` mention downgrade, you may mention review stayed read-only. ## Ha