pr-management

PR Management

Open pull requests, keep them current, and merge them once they are ready.

Prerequisites

• repo_owner and repo_name for the target repository
• The head branch must already be pushed before creating a PR
• GitHub token with repo write access

Workflow

Opening a PR

1. Call list_repo_labels to see the label names the repository defines
2. Call create_pr with title, body, head branch, base branch and labels
3. Pass draft=True while the work is still in progress
4. The mcp label is appended automatically, so do not pass it yourself

Updating a PR

1. Call update_pr to change any subset of the title, body, state, base branch and labels. This is the one to reach for, since it leaves the fields you omit alone
2. Call update_pr_description only when replacing both the title and the body together
3. Call set_pr_draft to mark a draft ready for review, or to put a PR back into draft
4. Call update_assignees to set the assignees
5. Call update_pr_branch when the base branch has moved on and the PR needs the latest upstream commits

Closing a PR

1. Call update_pr with state="closed". Reopen with state="open"
2. Closing is not merging. A closed PR keeps its branch and its comments

Merging a PR

1. Call get_pr_status_checks and require overall == "passing", per the pr-analysis skill
2. Confirm the review decision is an approval
3. Ask the user in chat and get an explicit yes before calling merge_pr. The tool does not prompt and the merge cannot be undone
4. Call merge_pr with an explicit commit_title

Tool Parameters

create_pr

Parameter	Type	Default	Description
repo_owner	str	-	GitHub organisation or username
repo_name	str	-	Repository name
title	str	-	PR title, see Title Convention
body	str	-	PR description in Markdown
head	str	-	Source branch name
base	str	-	Target branch name, e.g. main
draft	bool	False	Open as a draft PR
labels	list[str] | None	None	Labels to apply. Omit to leave the PR unlabelled