sol-loop

GPT 6.1 Sol reviews your change in rounds. Make the smallest changes that answer it, avoid scope creep, and push back when it is wrong.

Budget

• 3 rounds. Round 1 is full; later rounds check only changed code and open findings.
• 5 only if the user asks, or for security, permissions, auth, data loss, or state/concurrency while a blocker or should stays open with evidence.
• Stop early if a round returns only nits. Declined nits and comment, doc, or format-only fixes need no new round.
• One reviewer only. Sol must not start subagents or reviewers.
• Keep a ledger: id, severity, outcome, usage if returned. Never guess usage.

1. Scope

Run git status --short. Never stash, discard, or include unrelated changes; if they don't separate cleanly by path, stop and ask.

After git fetch origin, base is git merge-base HEAD origin/<PR base or default branch>. For a PR, HEAD must be the PR head or ahead only by this change. No remote: a base the user names, or HEAD for uncommitted changes only. The change is base to working tree, untracked files included; use the same diff every round.

State intent and out-of-scope in 1-2 sentences. Run the covering checks (swift build, script/test_quiet.sh --filter <Suite>); never send code the change breaks. Note missing or already-failing checks in the brief.

2. Start Sol

The reviewer is GPT 6.1 Sol, unless the user names another Sol version. Reach it the way your harness allows:

• Capy: a subagent or thread on model openai/gpt-6.1-sol; keep its path or code for later rounds.
• Cursor: a background agent or new chat with GPT 6.1 Sol selected.
• Claude Code and other harnesses without GPT models: Codex CLI, codex exec -m gpt-6.1-sol - with the brief on stdin (read-only sandbox by default). Note the session id it prints; codex exec resume <SESSION_ID> continues it.
• Anything else: give the user the brief to run in a Sol session and wait for the reply.