sol-loop

This is a workflow for making your code changes more correct before (or sometimes after) filing a pull request. tl;dr - use OpenAI's GPT Sol to review your code in a loop.

Make the most minimal possible changes to appease the Sol reviewers. Be careful of scope creep and don't be scared to push back.

Budget

• Default: 3 rounds total. Round 1 is full. Later rounds check only changed code and open findings.
• Extend to 5 only for security, permissions, auth, data loss, or state/concurrency, while a blocker or should stays open with evidence. Or when the user asks.
• 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 it.

1. Scope

Run git status --short. Do not stash, discard, or include unrelated changes. Limit review to the change paths if they separate cleanly. Otherwise stop and ask.

Find the base after git fetch origin:

• PR: gh pr view <n> --json baseRefName,headRefOid. Check out the branch only if clean. Confirm HEAD is the PR head, or ahead only by this change. Base: git merge-base HEAD origin/<baseRefName>.
• Local: git merge-base HEAD origin/<default-branch>. No remote: a base the user names, or HEAD for uncommitted changes only.

The change is base to working tree in those paths, with untracked files. Use one diff command all rounds. State intent and out-of-scope in 1-2 sentences. Run covering checks. Do not send code this change breaks. Note missing or pre-failing checks in the brief.

2. Start Sol