Update an existing pull request with new changes from the current branch using GitHub MCP tools. Use when the user asks to update a PR, refresh a pull request description, or sync PR details with the latest branch changes. Also use proactively after committing and pushing changes to a branch that has an open PR, to keep the description and diagrams in sync.
Update an existing pull request with new changes from the current branch using GitHub MCP tools.
IMPORTANT: Prefer the GitHub MCP server tools (mcp__github-mcp-server__*) for all GitHub operations. If MCP tools fail or are unavailable, fall back to the gh CLI.
Use ToolSearch to load these tools before calling them:
mcp__github-mcp-server__search_pull_requests — find PRs by branch namemcp__github-mcp-server__pull_request_read — get PR details, diff, filesmcp__github-mcp-server__update_pull_request — update PR title, body, stategh repo view --json owner,name,defaultBranchRef --jq '{org: .owner.login, repo: .name, base: .defaultBranchRef.name}'
<owner><repo><base-branch>git branch --show-currentmcp__github-mcp-server__search_pull_requests with query head:<branch-name> is:open, owner <owner>, repo <repo>
mcp__github-mcp-server__pull_request_read with method get to retrieve the title and bodygit push origin <branch-name>)mcp__github-mcp-server__pull_request_read with method get_diff and also run git diff --stat <base-branch>..HEAD locally
base.ref)git log --oneline <base-branch>..HEAD and check if any commits were already merged to the base branch via other PRs (look for PR merge indicators like (#NNN) suffixes in commit messages). These are inherited from a parent branch and should NOT be described in this PR. Only describe work that is unique to this branch."<PBI_TICKET> <title>"mcp__github-mcp-server__update_pull_request with:owner: <owner>repo: <repo>pullNumber: the PR numbertitle: the updated title (if changed)body: the updated descriptionpr-diagrams skill with the PR number
pr-diagrams skill saves files to docs/architecture/, commits, and pushes them before posting the PR comment — so the diagram source files are included in the PR diff[View Pull Request](https://github.com/<owner>/<repo>/pull/828)gh repo view (<owner>)gh repo view (<repo>)gh repo view (<base-branch>)gh CLI if MCP is unavailablegh CLI:
gh pr view --json number,title,body,baseRefName,headRefNamegh pr diff <number>gh pr edit <number> --title "<title>"gh pr edit <number> --body "<description>"gh is authenticated first with gh auth statusgh CLI also fails, inform the user they can update the PR manually on GitHub web interface<base-branch>, NOT incremental development changes(#NNN) PR suffixes in commit messages) must be excluded from the description. The PR should only cover the work done on this specific branch.