Make /review take in a summary of the issue against uncommitted changes #5598

What feature would you like to see?

Huge fan (and user) of /review (#5547). We have this unique use case where our project is comprised of 50+ git submodules (I haven't counted) where it's split up between the core app, frameworks, extensions, dependencies and so on.

Since changes made to the project may involve changes in various different git repositories, we need to run codex from the the base project repo. Although I've raised a related bug here, a number of times I find myself relying on the Use custom instructions with /review primarily because I've noticed:

• Without giving /review a custom set of instructions of what it should look out for, what changed, why we changed it, what our expectations are, what type of regression we're guarding against etc, the code review can at times miss these key areas.
• It does indeed return with useful reviews as if run in complete isolation, I've had much more success when I've given it a summary of the issue that we were trying to solve. This makes it zero in on all the various use-cases / edge-cases around the issue at hand

Please make it possible to enable / disable running a blinded-review vs a review + use summary from current chat / discussion

Since I run /new before I begin tackling a new issue and then a follow-up /review, I know this enhancement would mean there's nothing else poisoning the context and the review will be solely around changes codex made.

Additional information

No response