Awesome Reviewers expert instructions

Raw access

Everything on this site is a static file. No key, no rate limit, no client-side rendering required. Fetch one instruction, a whole domain, or the index and pull what you need.

Endpoints

PathTypeWhat it is
/raw/<slug>.md markdown One instruction, with a small front-matter header (domain, topic, language, source, updated).
/raw/bundles/<domain>.md markdown Every instruction in a domain, concatenated, each with a source comment.
/raw/index.json json Full index: slug, title, description, domain, topic, language, source, updated, raw URL.
/assets/data/search.json json Column-oriented index used by the search box. Smaller; no descriptions.
/llms.txt text Domain-grouped listing of the whole corpus with raw URLs.

Examples

# one instruction
curl https://awesomereviewers.com/raw/qwen-code-secure-boundary-enforcement.md

# a whole domain in one file
curl https://awesomereviewers.com/raw/bundles/llm-infra.md

# everything updated since a date, as slugs
curl -s https://awesomereviewers.com/raw/index.json \
  | jq -r '.entries[] | select(.updated >= "2026-01-01") | .slug'

# assemble a system prompt from one domain
curl -s https://awesomereviewers.com/raw/index.json \
  | jq -r '.entries[] | select(.domain == "orchestration") | .raw' \
  | xargs -n1 curl -s > orchestration.md

Freshness

Every instruction carries the date of the most recent review comment behind it, and every domain carries the newest date among its instructions. Both are exposed in /raw/index.json and in the front matter of each raw file, so a scheduled job can diff against its last run instead of refetching the corpus.

The corpus was last updated (2026-07-29).

From the repository

If you would rather not fetch over HTTP, the source of truth is _reviewers/: one markdown instruction per file, plus a sibling JSON file holding the review discussions it was derived from. Clone it and run python build_data.py to regenerate every artifact listed above locally.

Terms

Apache-2.0, same as the repository. The instructions are distilled from public review discussions; they are not official guidance from the projects they were derived from.