I've been seeing answers recently in the Low Quality and First Posts queues on SO that are only 2-4 lines of code, with no other explanation. My habit was to scroll down to the question and try and see if it seemed like the code did actually solve the problem. Sometimes it seems to; "How do I do X with a button?" Answer: 2-4 lines of code about buttons. So okay, maybe sometimes they're self-explanatory and don't absolutely require explanation (though that would of course make them better answers.) Generally I do end up approving these; sometimes I skip when I can't tell if they're legitimate answers or not. (Disclaimer: I've only had 2k privileges and been reviewing actively for <2 weeks.)
But just now I reviewed an answer that was 1 line of actual code (a function definition), with 2 more lines that were simply opening and closing braces. This made me pause and think "Is this a review audit?" But I stopped and looked at the question, and it did seem like it answered it, so I approved the post. But this has made me stop and think: should I be approving these as a rule? I mean...if they're helpful and give the OP the code they need, then even though you could say they are LQ, they're still an answer. But since some are very short, and this one was actually short enough to make me wonder if it was an audit.... I just want to check that I'm doing the right thing with these posts.
Approve, reject, or skip and let someone who knows the language take a look at it? I'm sure editing would be the preferred option, but I'm not always going to have the knowledge to edit explanation into every one of these answers I review.