Which checks should this change pass?
Pick the language of the files you changed. You get the checks 256 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 5832 of their code review discussions.
Languages
baseline checks: the most-run tool per check kind
Python
.py .pyi
ruff-formatruff-checkmypypytest
TypeScript
.ts .tsx .mts
prettiereslinttscvitest
JavaScript
.js .jsx .mjs
prettiereslintjest
Rust
.rs
rustfmtclippycargo-checkcargo-test
Go
.go
gofmtgolangci-lintgo-test
Java
.javano language-specific tool detected; prompts
Kotlin
.kt .ktsno language-specific tool detected; prompts
Swift
.swiftno language-specific tool detected; prompts
C++
.cc .cpp .cxxno language-specific tool detected; prompts
C
.c .hno language-specific tool detected; prompts
C#
.csno language-specific tool detected; prompts
Ruby
.rbno language-specific tool detected; prompts
PHP
.phpno language-specific tool detected; prompts
Shell
.sh .bash .zshno language-specific tool detected; prompts
SQL
.sqlno language-specific tool detected; prompts
YAML and CI workflows
.yml .yaml
prettier
JSON and TOML
.json .toml
prettier
Dockerfile
Dockerfile .dockerfileno language-specific tool detected; prompts
Markdown and docs
.md .mdx .rst
prettier
What the change touches
each language page applies this to its own tools
| The change touches | Add these checks | Prompt topics |
|---|---|---|
| Any change | Formatting, Linting, Type checking, Unit and integration tests | Code Style, Naming Conventions |
| Authentication, input handling, secrets, permissions | Security scanning, Secret scanning, Dependency audit | Security |
| Public APIs, signatures, error paths, nullability | Type checking, Unit and integration tests, Property-based tests | API, Error Handling, Null Handling |
| Service and framework code | Unit and integration tests, Version and platform matrix | Fastify, NestJS, Spring, Axum, Celery, Temporal |
| Algorithms, parsers, data transforms | Property-based tests, Fuzzing, Mutation testing, Proofs and specifications | Algorithms |
| Threads, async code, locks, shared state | Concurrency model checking, Undefined-behaviour detection, Property-based tests | Concurrency |
| Network calls, retries, timeouts, protocols | Unit and integration tests, Fuzzing | Networking, Axios |
| UI components and pages | End-to-end browser tests, Linting | React, Next, Next.js, Vue, Angular |
| Databases, migrations, caching | Unit and integration tests, Version and platform matrix | Database, Migrations, Caching |
| Hot paths and performance | none detected; prompts only | Performance Optimization |
| Model, prompt and LLM code | Unit and integration tests | AI, Pytorch |
| Logging, metrics, tracing | none detected; prompts only | Logging, Observability |
| CI workflows and configuration files | CI workflow linting, File hygiene | CI/CD, Configurations |
| Dependencies and lockfiles | Dependency audit, Lockfile consistency, Version and platform matrix | |
| The tests themselves | Mutation testing, Version and platform matrix | Testing |
| Documentation and comments | Docs build, Spelling | Documentation |
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/oh-my-pi-changelog-entry-conventions.mdStatic files: no key, no rate limit. Every page also links its markdown version.
Verification methods
Formal verification and model checking
3% of reposProves or exhaustively explores properties: model checking, proofs, undefined-behaviour interpreters.
Static analysis
87% of reposReads the code without running it: linters, type checkers, security and workflow scanners.
Testing
80% of reposRuns the code: unit and integration tests, browser tests, property-based tests, fuzzing, mutation testing.
Formatting and hygiene
64% of reposNormalises layout, spelling and file hygiene so the diff only shows what changed.
Supply chain
21% of reposChecks dependencies: known vulnerabilities, disallowed licenses, lockfiles that disagree with manifests.
Review prompts
Agent loops, tool calling, prompt and context assembly, agent SDKs and coding assistants.
Inference servers, model gateways and routers, KV caching, retrieval and ingestion pipelines.
Training and inference frameworks, tensor and kernel code, ML platforms and pipelines.
Kubernetes, schedulers, service meshes, container tooling, workflow and job engines.
Infrastructure as code, cloud SDKs, edge runtimes, proxies, gateways and tunnels.
Query engines, storage, replication, streaming, ORMs and analytics backends.
Metrics, tracing, logging, error tracking and instrumentation of production systems.
Static analysis, cloud posture scanning, authentication, authorization and secrets handling.
Interpreters, compilers, async runtimes, parsers and low-level systems code.
Editors, terminals, build systems, package managers, linters, formatters and test runners.
Web and mobile frameworks, component libraries, API layers and product codebases.
Reference material, curated lists and learning resources — mostly writing and structure guidance.