review-sdk-update-pr

name	review-sdk-update-pr
description	Review SDK docs update pull requests for ios, android, flutter, expo, or react-native in this repository. Use when asked to verify completeness and correctness of an SDK docs version bump by checking PR changes against upstream SDK git diff and changelog entries.

Review SDK Update PR

This review skill validates work produced with update-sdk-docs. Read ../update-sdk-docs/SKILL.md first, then use it as the canonical checklist.

Required Inputs

1. sdk
2. newVersion
3. PR branch or PR number (or confirmation that HEAD is the candidate branch)

Review Workflow

1. Establish baseline

• Check out the PR branch.
• Run bun run download:references.
• Identify previousVersion from the base branch in:
  • content/docs/<sdk>/index.mdx
  • content/docs/<sdk>/sdk-reference/index.mdx
• Confirm the PR updates both files to newVersion.

2. Verify upstream source changes

• In reference/<sdk>/, fetch tags and compute <prevTag>...<newTag> diff (expo tags are v-prefixed).
• Review:
  • git log --oneline <prevTag>..<newTag>
  • git diff --stat <prevTag>...<newTag>
  • Raw diff for API/setup changes
  • Upstream changelog entry for newVersion
• Build your own expected docs checklist before judging the PR.

3. Audit PR changes for completeness and correctness

• Compare changed docs against your expected checklist and the update-sdk-docs workflow.
• Confirm changelog update is additive (history preserved), not replaced by only one new entry.
• Confirm commit message and PR title format: feat(<sdk>): update for <newVersion>.
• For android, explicitly verify content/docs/android/quickstart/install.mdx reflects the new version.
• Check for stale version strings, outdated code samples, missing guide updates, and navigation/meta issues.

4. Validate execution quality

• Run bun run build:cf.
• Run bun test.
• Flag failures and note any verification steps the PR author skipped.

Reporting Format

• Report findings first, ordered by severity.
• For each finding include:
  • Why it is incorrect or missing
  • Exact file path(s) with line references
  • Concrete fix guidance
• If no findings exist, state that explicitly and list residual risk areas reviewed.

Common Misses to Hunt

• Upstream API or behavior changes present in diff/changelog but absent from docs.
• Only updating version markers while missing setup or guide updates.
• Changelog history truncated by replacing old entries.
• Android install page not updated.
• Reviewing only file stats without checking raw upstream diff.