claudex-second-opinion

1# ClauDex Second Opinion
2 
3## Overview
4 
5When a change is substantial or risky, suggest a cross-model review with
6`/claudex:verdict`. Two frontier models trained by rival labs have *different*
7blind spots — when both flag the same line it's the strongest free review
8signal there is, and where they disagree is exactly where a human should look.
9 
10**Hard rule: never run `codex` yourself under this skill.** A cross-model
11review spends the user's Codex quota and adds real latency. Explicit
12invocation is consent — your job here is one well-timed suggestion, nothing more.
13 
14## When to suggest
15 
16- The change touches auth, payments, data deletion, migrations, concurrency, or crypto
17- A multi-file refactor or roughly 150+ changed lines
18- A bug fix where the root cause was never fully confirmed
19- The user sounds unsure ("I think this works", "hopefully that's it")
20- The user is weighing an architectural choice *before* code exists — then
21  the right suggestion is `/claudex:debate <the decision>`, not a verdict
22  (a debate needs a question, not a diff)
23 
24## When to stay quiet
25 
26- Trivial or mechanical changes: docs, formatting, renames, config bumps
27- As far as you can tell from the visible conversation, a ClauDex command
28  already ran on this diff (best-effort — don't re-suggest what the user
29  just did)
30- The Codex CLI isn't installed — at most, mention `/claudex:setup` once in
31  the visible conversation, then drop it
32 
33## How to suggest
34…