Q:

If SO had a standard off-topic reason for code review requests, how should it be worded?

We have long been fighting a battle against Stack Overflow users who vote to close questions with custom reasons like

I'm voting to close this question as off-topic because it belongs on Code Review.

Not only do these messages contradict Stack Exchange policy, they also fail to convey the purpose and scope of Code Review.  Misconceptions abound.
We've tried educating Stack Overflow users, but memes are hard to kill, and we're outnumbered.  I've suggested banning "I'm voting to close this question as off-topic because it belongs on …", but there is no indication that Stack Exchange will implement such a ban anytime soon.
So, I think it's time to switch tactics.
What if Stack Overflow redefined its scope to make code review requests explicitly off-topic?1  That is, de facto, what is happening on Stack Overflow, but each Stack Overflow user expresses the reason in their own words, poorly.
How would we, as the Code Review community, recommend that the close reason be worded?  This is our chance to craft a standard elevator pitch.

1 Note that this is a decision to be made by the Stack Overflow community.  This discussion is a preliminary step.  Once Code Review develops consensus around a wording, we'll make a proposal on Stack Overflow Meta.

A:

Some wording we came up with in chat:

Questions about reviewing or improving existing, working code and lacking a specific question statement are off-topic for Stack Overflow. You may be able to get help on Code Review.

The basis of this wording is to build it around the same wording as the Super User close reason:

Questions about general computing hardware and software are off-topic for Stack Overflow unless they directly involve tools used primarily for programming. You may be able to get help on Super User.

The idea is to convey two things:

That the question is off-topic on SO;
That the question could be on-topic on CR;

This does the same thing as the Super User close reason, which indicates what makes a question off-topic on SO, and on-topic on SU.

A:

Partly based on earlier proposal by EBrown in chat:

Without specific programming questions this is off-topic for Stack Overflow. However if your code works as intended, you may get a review and evaluation of it at Code Review.

Without **specific programming questions** this is off-topic for Stack Overflow. 
However if **your code works as intended**,
you may get a **review and evaluation** of it at
[Code Review](https://codereview.stackexchange.com/about).

This, to me, gives a good reason of why it is off topic on Stack Overflow as it lacking questions to be answered, and at the same it counters the main reasons for closing questions here at Code Review.

A:

I think you should be focusing on closing questions, not migrating them.
Stack Overflow has a very poor history of successful question migrations (especially to Programmers); that's why the process is intentionally difficult.  A bot called Duga captures suggestions for migration in the question comments for both Programmers and Code Review; I will let the Code Review folks state what their percentage is, but for suggestions for migration to Programmers captured by the bot, 95 to 99 percent of them are not only poor candidates for migration, but are also closeable on Stack Overflow under the current rules.
Further, you already have legitimate means to close these questions on Stack Overflow without adding any additional close reasons. They already qualify for the "Questions Asking for Code" close reason (they don't meet all of the requirements), and for being Too Broad.  Take your pick.
Finally, if someone wants to try their luck, they're perfectly capable of re-asking their question on Code Review themselves.
Verdict:  Stack Overflow doesn't need another close reason.  The current crop of close reasons already adequately suffices.

