Awesome Reviewers

Verifying JSON and TOML changes

Files: .json, .toml. Derived from 8 scanned source repositories and 251 review prompts on https://awesomereviewers.com. Page: https://awesomereviewers.com/verify/config/

How to use this: run every check under Run on every change. Then, for each section under Add when the change touches that describes your diff, run its checks too. Checks catch what a tool can find; then apply the listed review prompts for what tools miss (fetch each prompt’s raw URL).

Usage is the share of scanned repositories in this language that run the tool. A missing tool means no scanned repository runs one the scanner recognises: fall back to the prompts.

Run on every change

Review prompts (37 in total, most discussed first):

Add when the change touches

Authentication, input handling, secrets, permissions

Review prompts (23 in total, most discussed first):

Public APIs, signatures, error paths, nullability

Review prompts (17 in total, most discussed first):

Service and framework code

Algorithms, parsers, data transforms

Review prompts (2 in total, most discussed first):

Threads, async code, locks, shared state

Network calls, retries, timeouts, protocols

Review prompts (1 in total, most discussed first):

UI components and pages

Review prompts (1 in total, most discussed first):

Databases, migrations, caching

Review prompts (5 in total, most discussed first):

Model, prompt and LLM code

Review prompts (9 in total, most discussed first):

CI workflows and configuration files

Review prompts (135 in total, most discussed first):

Dependencies and lockfiles

The tests themselves

Review prompts (13 in total, most discussed first):

Documentation and comments

Review prompts (8 in total, most discussed first):

Source repositories

home-assistant/core, zed-industries/zed, appwrite/appwrite, juspay/hyperswitch, bytedance/UI-TARS-desktop, Azure/azure-quickstart-templates, the-pr-agent/pr-agent, Azure/Azure-Sentinel