new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Expo · Router · all subjects

out of scope

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

expo-review skill: source modes

The expo-review skill supports three source modes: PR mode (identified by PR number 1-2147483647 or URL matching ^https://github\.com/expo/expo/pull/([0-9]+)/?$), staged mode (--staged flag reviews index against HEAD, excluding unstaged and untracked files), and ref-range mode (--base <ref> and optional --head <ref> to review a local range). With none of these, the default mode reviews the local working tree against its merge base, including committed branch changes plus staged, unstaged, and untracked non-ignored files.

expo-review skill: available agents

The expo-review skill accepts these Expo reviewer agents: config-plugins, correctness, correctness-android, correctness-ios, correctness-js, docs, public-api, and security. The 'all' keyword selects all agents. The --agents flag takes a comma-separated list of agent names in the user's specified order.

expo-review skill: posting behavior for PR previews

For a validated Expo PR preview without --post, --save-review is passed by default, which writes an ignored, owner-readable artifact under .expo-code-review/.runs/deferred/ but does not write to GitHub. The explicit --post flag can only be used with a validated Expo PR and requires explicit user authorization in the current request to publish the review to GitHub. The --no-save-review flag opts out of saving for a validated Expo PR preview without passing --post.

expo-review skill: ref validation requirements

Before passing a ref to the review command, it must be validated: 1–200 characters long, start with an ASCII alphanumeric character, and contain only ASCII alphanumerics plus . _ / @ { } ^ ~ : or - characters. Verification is performed via 'git rev-parse --verify --end-of-options' without changing the working tree. This validation excludes quotes, whitespace, shell substitutions, option-like values, and control operators.

expo-review skill: command structure

The review command is run from the repository root as: ./scripts/expo-code-review ecr review --json --no-fail [validated source flags] [--route | --agents <ids>] [--save-review | --post]. For a PR, validated source flags must include --repo expo/expo --pr <number>. The --no-fail flag prevents a request_changes result from appearing as an execution failure; the JSON decision remains authoritative.

Give your agent this brain

out of scope — Expo · Router