expo-docs-reviewlisted

# Expo Docs Review **Context before critique. Read the PR description and the changed file in full before flagging individual lines.** ## When NOT to Use - The PR touches files outside `expo/docs/pages/`. This skill only knows about `.mdx` files under that path. - The PR is on a private repo or GitHub Enterprise. Public Expo PRs only. - `gh pr view` returns an authentication error or "Could not resolve to a PullRequest". Tell the user to run `gh auth status` / `gh auth refresh` and stop. ## Input A public GitHub PR URL. Accepted forms: - `https://github.com/expo/expo/pull/30000` - `expo/expo#30000` - A bare PR number, when the user has already established the repo in context ## References - **`../../../references/expo-docs-style-guide.md`** — prose: voice, tone, punctuation, formatting, glossary, anti-patterns. - **`../../../references/expo-docs-components.md`** — MDX components: catalog, mandatory-usage rules, prop tables, gotchas. - **`../../../references/expo-docs-review-comments.md`** — comment body format: severity tag, `suggestion` blocks, single vs. multi-line. - **`../../../references/expo-docs-review-output.md`** — output: JSON schema, GitHub-API fields, verdict mapping. ## Four-phase workflow ### Phase 1: Fetch and Context Use the `gh` CLI for GitHub fetches. 1. **Resolve the PR.** Parse `{owner}/{repo}/{number}` from the user's input. 2. **Fetch PR metadata:** ```sh gh pr view {number} --repo {owner}/{repo} --json title,body,baseRefOid,headRefOid