For the complete documentation index, see llms.txt. This page is also available as Markdown.

Review pattern mining

Stop repeating the same code-review comment. A scheduled review miner reads recent reviews, finds the feedback that keeps coming up, and proposes a lint rule for it.

Goal: Stop reviewers repeating the same comment by turning it into a rule.

What it does

Weekly, a schedule reads the last 50 code reviews and looks for feedback that keeps coming up. If reviewers keep saying the same thing, the plugin proposes a lint rule, an automated check, or a documented convention to address it. Reviewers spend less time repeating the same comment and more time on the decisions that need their judgment.

The plugin

tessl/review-miner reads recent review comments, groups the recurring ones, and proposes a rule, check, or convention for each. Install it with:

$ tessl install tessl/review-miner

Define the schedule

Run it every Monday at 9:00 UTC. Add this entry to the schedules block in your project's tessl.json, and keep any other entries already in that block. Replace production with the name of your environment (see the Schedules overview for the prerequisites).

1

Add the schedule entry

{
  "schedules": {
    "review-miner": {
      "skill": "tessl/review-miner",
      "schedule": "weekly on monday at 09:00",
      "environment": "production"
    }
  }
}
2

Validate and push

Validation always checks the local file. For an authenticated linked project that can reach Tessl, it also gives an advisory warning when current workspace capacity may not accommodate additional schedules. Commit and push the change, then confirm Tessl applied the schedule in your workspace before checking its run history.

$ tessl schedule validate
$ git add tessl.json
$ git commit -m "chore(docs): add review miner schedule"
$ git push
3

Check the runs

Open the schedule in the web app, or run tessl schedule runs <id> to see its run history.

Customize with instructions

Focus the search on one area by adding instructions to the same schedule entry. Keep all other entries in the schedules block:

{
  "schedules": {
    "review-miner": {
      "skill": "tessl/review-miner",
      "schedule": "weekly on monday at 09:00",
      "environment": "production",
      "instructions": "Only look for repeated feedback about error handling and logging"
    }
  }
}

Create your own

Want a different behavior? Create your own plugin that reads recent review comments and proposes a rule your way.

Last updated