Note: For chat-like discussions of this subject, let's use this Discuss Close Reasons chat room
Code Review currently has three standard off-topic reasons:
- Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.
- Questions must involve real code that you own or maintain. Pseudocode, hypothetical code, or stub code should be replaced by a concrete example. Questions seeking an explanation of someone else's code are also off-topic.
- Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.
While sites are encouraged to stick to three, we can have up to five standard reasons, if we can justify it. With that in mind, how would you modify the list?
For your reference, here is the relevant excerpt from the Help Center:
To be on-topic the answer must be "yes" to all questions:
- Is code included directly in my question? (See Make sure you include your code in your question below.)
- Am I an owner or maintainer of the code?
- Is it actual code from a project rather than pseudo-code or example code?
- Do I want the code to be good code? (i.e. not code-golfing, obfuscation, or similar)
- To the best of my knowledge, does the code work as intended?
- Do I want feedback about any or all facets of the code?
If you answered "yes" to all the above questions, your question is on-topic for Code Review.
Note that the max-length for a close reason is 400 characters (including markdown).