One of the close reasons that exists is:
Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. Such questions may be suitable for Stack Overflow or Programmers. After the question has been edited to contain working code, we will consider reopening it.
While I'm having trouble finding it off hand, I have seen more than a few questions that were reposted on Programmers.SE after having been closed with this reason. I'm sure there are some on Stack Overflow.
Unfortunately, as I am sure you are aware, that people don't read the help/on-topic page of the help center (if they did, they wouldn't have asked the question on Code Review in the first place). This also means they don't read the help/on-topic on Programmers either when reposting their question.
I've cast some close votes on questions in recent times that were debugging questions that had nothing to do with the design.
Could the close reason, instead of linking to the site link to the on topic definition for the site. This might help people realize the better location.
Ideally, a moderator would never close with this reason because they have the ability to migrate the question to the proper site (I assume that when the site finishes with the graduation ceremony, the migration paths will be added and this close reason will be removed - on Programmers.SE we had some issues with people closing an early version of "go repost somewhere else" (see graph in associated question and the jump for "belongs" (purple - migration) which jumped after the "questions about specific programming problems" (light blue) was removed). So, when you graduate, remove this close reason and let people migrate instead.
In theory, the moderator will have a better idea if the question is a design issue or a code / debug issue than the OP has (when they don't read the site description) and be able to move it more smoothly to the proper site than asking the OP to repost the question. This is especially helpful when there is additional clarifying material in the comments, or it was reformatted. Also, if the question is unclear, too broad, or primarily opinion, no matter if it was on-topic-ish on the other site, the moderator would close it appropriately rather than bouncing the OP around to other sites.
On P.SE, we've tended to find that when a close reason or comment suggests someone to post on another site, it's rarely a good thing and often just leads to a much poorer user experience ("well, the guys on Stack Overflow told me to repost on Programmers after I got the question closed on Code Review" when the original problem is it is unclear to begin with).
Thus, in general, I'd urge you to strongly reconsider having this close reason at all. If something belongs somewhere else, flag it for migration. Closing it with "go repost it over there" doesn't allow for the feedback cycles of rejected migrations and attention to why things are getting moved. These close reasons are often a "we don't want to deal with it, so go over there" - which isn't fair to the OP, or the over there which now has to deal with someone who got the post closed again (and isn't happy about it at all).
If a SE employee/dev can poke at this, it might be useful to try to track down the "the question was closed with this reason here, reposted on [SO|P.SE] and its fate there." I am aware of the difficulty of the matching posts between the sites and might suggest something like 'the first 42 bytes of the question match 42 bytes of a question (anywhere in the post) on another site' as criteria for matching.
This would help get a better idea of how big the repost rather than migrate trend is and if there is any real concern to be worried about this.