# Pr > Create, list, check out, review, or merge GitHub pull requests using GitHub CLI. Use when the user wants any pull-request workflow, not when they want to manage issues, releases, or local-only commits. - Skill: `zai-org/pr` (Agent Skill) - Install (CLI): `npx skillmds@latest add zai-org/pr` - Raw SKILL.md: https://api.skillmd.com/api/skills/zai-org/pr/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: zai-org (https://skillmd.com/u/zai-org) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/zai-org/pr --- # Pull Requests Work with pull requests using the GitHub CLI (`gh`): create, list, check out, review, and merge. ## Arguments $ARGUMENTS **Format:** ` [args...]` - `create [base_branch]` - Create a pull request - `list [filters...]` - List pull requests with filters - `checkout ` - Check out a PR locally - `review [approve|comment|request-changes] [comment]` - Submit a review - `merge [--squash|--rebase|--merge] [--delete-branch]` - Merge a PR ## Examples ``` /github:pr create feature/user-auth /github:pr create feature/user-auth develop /github:pr list --reviewer @me /github:pr list --state merged --author octocat /github:pr checkout 123 /github:pr review 123 approve "LGTM! Great work on the refactor." /github:pr review 123 request-changes "Please add unit tests" /github:pr merge 123 --squash --delete-branch ``` ## Instructions ### Required GitHub CLI preflight Before any workflow step, read `../../references/github-cli-preflight.md` and complete it. Do not run workflow commands until `gh` installation and authentication are verified. ### Create 1. **Validate and resolve branches:** ```bash git check-ref-format --branch git check-ref-format --branch git rev-parse --verify "^{commit}" git rev-parse --verify "^{commit}" || git rev-parse --verify "origin/^{commit}" ``` If no base branch was supplied, obtain it from: ```bash gh repo view --json defaultBranchRef --jq .defaultBranchRef.name ``` Store the successfully resolved local or `origin/` base ref as `` and use it consistently in subsequent `git log` commands. 2. **Check if head branch has commits ahead of base:** ```bash git log .. --oneline ``` If there are none, report "Error: No commits between and ". 3. **Generate PR title and description:** Analyze the commits between base and head, create a concise title, and write a description that summarizes what changed, why, and any testing done: ```markdown ## Summary Brief description of what this PR does. ## Changes - Change 1 - Change 2 ## Testing - [ ] Tested locally - [ ] Unit tests pass ``` 4. **Ensure the head exists remotely:** Check whether the head branch has an upstream. If it does not, show the repository and branch and ask for confirmation before: ```bash git push -u origin ``` 5. **Prepare and confirm:** Write the generated title and description to separate temporary files. Show the verified repository, base/head branches, title, and whether the PR will be draft. Require explicit confirmation before creating the PR. 6. **Create the PR safely:** Read the title from its file into a quoted variable and pass the body by file: ```bash pr_title=$(<"$title_file") gh pr create --base --head \ --title "$pr_title" --body-file ``` If the PR already exists, report the existing PR URL instead. 7. **Report the PR URL** to the user. ### List 1. **Parse filter arguments:** `--author`, `--assignee`, `--state` (open/closed/merged/all), `--label`, `--base`, `--draft`, `--search `, `--limit ` (default 30). `@me` means the current authenticated user. 2. **Build and execute query:** ```bash gh pr list [--author ] [--assignee ] [--state ] [--label