autoreview-sdk-update-pr

name	autoreview-sdk-update-pr
description	Auto-review SDK docs update PRs for ios, android, flutter, expo, or react-native. Use this as a thin autoreview-style wrapper around review-sdk-update-pr: launch fresh read-only reviews, fix only verified findings locally, and repeat until clean.

Auto Review SDK Update PR

Run an autoreview-style closeout loop for SDK docs update PRs. This skill is only the coordinator; ../review-sdk-update-pr/SKILL.md is the source of truth for SDK/version/tag/changelog rules, expected docs checks, and verification requirements.

Use when:

• user asks for autoreview-sdk-update-pr
• user wants review-sdk-update-pr run, valid findings fixed, and the review repeated until clean
• closing out an SDK docs update PR after CI, bot comments, or manual review notes

Contract

• Start each review round with a fresh read-only sub-agent.
• Tell the sub-agent to read and follow ../review-sdk-update-pr/SKILL.md completely.
• Treat review output as advisory; verify each finding locally before editing.
• Fix only concrete, valid issues with minimal local changes.
• After any fix, run the verification required by review-sdk-update-pr, then start another fresh review round.
• Stop when a fresh review reports no valid remaining issues.
• Do not commit, push, create a PR, deploy, rerun remote CI, or resolve GitHub threads unless the user explicitly asks.

Inputs

Collect the inputs needed by review-sdk-update-pr:

1. SDK
2. New version
3. Review target: PR number, branch, or current HEAD / working tree
4. Optional reported issues from user notes, CI notes, GitHub comments, or files under .context/attachments/comments/

If an input cannot be inferred from branch name, changed files, version markers, PR metadata, or user notes, ask one concise question.

Workflow

1. Establish the target:

   • Check git status --short --branch.
   • Identify the PR/base branch when available.
   • Inspect changed files against the base and note dirty working-tree files.
   • Read any user-provided notes or comment files.

2. Launch a fresh read-only review sub-agent with:

   • repository path
   • base branch or comparison ref
   • candidate branch / PR / working tree
   • SDK and new version
   • changed files
   • reported issues, if any
   • instruction to follow ../review-sdk-update-pr/SKILL.md and end with Verdict: CLEAN or Verdict: NEEDS_WORK

3. Triage the result in the parent session:

   • Accept findings only after verifying them against the repo and upstream SDK references.
   • Reject speculative, stale, already-fixed, duplicated, or out-of-scope findings.
   • Apply minimal local fixes for accepted findings.

4. If files changed:

   • Run the verification required by review-sdk-update-pr.
   • Start a new fresh review round on the updated working tree.

5. Stop when a fresh round is clean.

Final Report

Include:

• review target and base
• number of review rounds
• final verdict
• accepted findings and local fixes
• rejected findings, if any
• verification results
• current git status

State clearly whether any fixes remain local and uncommitted.