interrogatelisted
Install: claude install-skill ychampion/ystack
# Interrogate
One reviewer has blind spots. A second reviewer from the same model family tends to share them.
Reviewers from different families, briefed identically and kept apart, miss different things. The lead
then treats every finding as a claim to check, not a vote to count.
## When it applies
- A non-trivial change that is costly to get wrong: auth, permissions, payments, migrations, storage,
concurrency, parsers and sanitizers, anything that deletes.
- A change you wrote yourself and now can't see fresh.
- The user asks for a second opinion.
Skip it for small, low-stakes diffs. One good reviewer is enough there, and this costs at least two
full reviews.
## Reviewers
Use two by default and three at most. Pick them from different model families:
| You are running in | Reviewer A | Reviewer B |
| --- | --- | --- |
| Claude Code | a subagent on your strongest Claude model | `codex exec` with a read-only sandbox |
| Codex | yourself, in a fresh context | `claude -p` with read-only tools |
| OpenCode or other | a subagent on one provider | a subagent on another provider |
Use the CLIs you're already logged in to. Don't spend a paid API key on this without the user's okay.
If only one model family is available, use one reviewer per family you do have, and say in the report
that the review isn't cross-family.
## Procedure
### 1. Write one brief and give it to every reviewer, unchanged
```
Review this change for defects: <diff command or file list, base..head>.
Con