Home

Welcome to the SOCVR-Chatbot wiki!

See the links on the right to get around.

---

The bot aides the reviewers of the close vote room in performing their daily task of spending 40 close votes. As a registered user the bot will accept your "starting" command (among [others](wiki/User Commands)) and listen for any messages you post when you pass/fail an audit, in addition to when you have finished reviewing (the so called "triggers").

##Initial workflow If you want to get started with the bot make sure you request to be registered first. Ping one of the room owners to get your account added. After that you can use the [registered commands](wiki/User Commands).

##Daily workflow Tell the bot when you start doing your daily CV reviewing by issuing the following command,

@Closey starting

You can also ask the bot for the current tag to filter on (to make sure your close votes count). Additionally, keep your eye on the starboard for additional, out-of-band requests.

When you hit an audit and pass it (or fail) post a message with the real tag of the question, for example,

@Closey passed Haskell audit

When you have finished reviewing a particular tag, copy the "There are no items for you to review, matching the filter [...]" message and post it in the room:

@Closey There are no items for you to review, matching the filter "off-topic, unclear what you're asking, too broad, primarily opinion-based; [web-applications]"

After using all your votes or reviews, paste the final message to trigger the bot to end your review session. (Doing so enables the bot to calculate you average speed.)

@Closey Thank you for reviewing 40 close votes today; come back in 5 hours to continue reviewing

The bot will then respond with:

Thanks for reviewing! To see more information use the command last session stats.

After that you can issue the command,

@Closey last session stats

To have the bot print your average reviewing speed:

Your last completed review session ended 8 seconds ago and lasted 30 minutes and 40 seconds. You reviewed 40 items, averaging a review every 46 seconds.

That is basically it. Doing so will store enough data so the other commands like completed tags and audit stats make sense.

Happy reviewing!