Which checks should this change pass?
Pick the language of the files you changed. You get the checks production repositories actually run on that code — tool, command, exit codes, autofix — then the checks to add for what the change touches, and the review prompts for what no tool catches. Checks come from their CI workflows and hooks; prompts from of their code review discussions.
Languages
baseline checks: the most-run tool per check kind
What the change touches
each language page applies this to its own tools
| The change touches | Add these checks | Prompt topics |
|---|
For agents
# 1. map changed files to languages, find the playbook
curl https://awesomereviewers.com/raw/verify/index.json | jq '.extensions'
# 2. load the playbook: checks per kind, commands, exit codes, then prompts
curl https://awesomereviewers.com/raw/verify/python.md
# 3. fetch the prompts that match the change
curl https://awesomereviewers.com/raw/.mdStatic files: no key, no rate limit. Every page also links its markdown version.