Picking a /code-review Effort Level for the Right Moment

You're working two different moments on the same day:

(a) Mid-refactor on a feature branch, still iterating — you want a quick sanity pass after each meaningful chunk before moving to the next one.

(b) About to open a PR for a change to the payments-refund flow that also touches shared currency-conversion code in three files.

1. Which /code-review effort level fits (a), and what specifically does that level trade away compared to a higher one?
2. Which effort level fits (b)? Would you consider /code-review ultra here — and under what condition would you skip it even for payments-adjacent code?
3. Later that day, in scenario (b), you run /code-review with no level argument and it silently reviews at low effort — the level you happened to type days earlier while working on an unrelated docs-only branch. Explain why this happened, and what practice prevents it from happening again on something that matters.