Rikki

Rikki is the friendly neighborhood robot nitpicker.

Rikki's comments are open source, and we welcome improvements of all kinds.

If you find typos, or if something is poorly worded, confusing, or incorrect, please file an issue or submit a pull request.

How it works

When someone submits a solution to exercism, the uuid of the submission gets placed in a queue implemented in redis.

Rikki pulls the uuid off the queue, makes a request to exercism.io's API to get the code, then submits the code to the analysseur API.

Analysseur uses analyzers/rules defined in the exercism-analysis repository, and responds with a list of violations. Each violation consists of type and a possible list of keys.

{
  "results":[
    {
      "type": "enumerable_condition",
      "keys": [
        "enumerable_condition"
      ]
    }
  ]
}

The comments/ directory of the rikki project contains a directory for each type, and a markdown file for each key.

The worker chooses one key at random and submits the contents of the markdown file as a comment to the exercism.io.

Usage

$ go install github.com/exercism/rikki
$ rikki

By default the worker runs against

• redis: localhost:6379
• exercism: localhost:4567
• analysseur: localhost:8989

These can be overridden using command-line flags:

$ ./rikki -redis=redis://user:pass@host:port/db/ -exercism=http://exercism.io -analysseur=http://analysseur.exercism.io

Enqueuing a Job

Start the console in exercism, find the uuid (a.k.a. key) of the submission you wish to process, and enqueue the job with:

Jobs::Analyze.perform_async(uuid)