stellar-docs-pr-review

Work through the issues assigned to the user on the stellar/stellar-docs repo: find the open issues assigned to them, pick one (or go oldest-first), understand what it asks, create a branch, implement a best-effort docs fix following the repo's conventions, verify it, commit, and automatically open a PR that links the issue and flags any assumptions — then hand the new PR to the stellar-docs-pr-review skill for preview testing. Use whenever the user asks you to work on / solve / fix / clear the issues assigned to them on stellar-docs, "take a look at my issues," or turn a specific stellar-docs issue into a PR. This is the write-and-open-PR counterpart to stellar-docs-pr-review (which only reviews existing PRs). Do NOT use for reviewing/merging PRs (use stellar-docs-pr-review), for non-stellar-docs repos, or for issues that require a product/design decision rather than a docs change.

Review pull requests on the stellar/stellar-docs repo as a maintainer would. Works two ways: given a specific PR URL/number, evaluate just that one; or given no specific PR, find every PR awaiting the user's review and work through them one at a time. For each PR: pull context, read the repo's contribution guidance, test what it changes on its Kube preview build (pagination, sidebar labels, breadcrumbs, page parity vs production), verify factual/Stellar claims with the Raven MCP, then approve + merge when confident, comment and hand off when something needs a human, or close it when it's a duplicate — giving a very short report after each PR before the next. Use whenever the user pastes a stellar-docs PR link, or asks you to review/triage/clear the PRs waiting on them, work their review queue, or look at what's waiting for them on stellar-docs. Do NOT use for writing new docs content, for non-stellar-docs repos, or for opening PRs from issues.