pr-checkout

Fetch and checkout a GitHub pull request by number into a local branch.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/lorrandavid/.dotfiles --skill pr-checkout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-checkout
Source: https://github.com/lorrandavid/.dotfiles/tree/main/.config/.copilot/skills/pr-checkout
Command: npx skills add https://github.com/lorrandavid/.dotfiles --skill pr-checkout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and checkout a GitHub pull request by number in a repository, enabling quick review and testing without manual branch management.

Core Features & Use Cases

  • Fetch PR data from origin using the PR number and create a local tracking branch (pr-<number>).
  • Checkout the fetched PR branch to switch context for review.
  • Use case: developers can rapidly jump into the exact PR work-in-progress to perform code review, tests, or demonstrations.

Quick Start

Checkout pull request number 42 in the current repository.

Frequently Asked Questions about pr-checkout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch and checkout a GitHub pull request by number in one step?

To fetch and checkout a GitHub pull request by number, supply the PR number as an integer parameter. The skill runs git fetch on origin and creates a local tracking branch named pr-<number>, then switches to it for review.

What is the easiest way to checkout a pull request locally for code review?

Checkinging out a pull request locally for code review is done by providing the PR number. The skill fetches the PR data and checks out the branch automatically, bypassing manual git branch management.

Do I need any specific git configuration to checkout a PR by number?

To checkout a PR by number, you need an existing local repository connected to the GitHub origin. The skill requires a valid pr_number integer parameter and validates that the fetch and checkout operations succeed in your current workspace.

Can I use this to checkout pull requests from any remote repository?

Fetching pull requests is constrained to git fetch and git checkout operations applied to the current workspace. It targets the origin remote configured in your local repository to pull the PR data.

Why does my pull request checkout fail when using a PR number?

Pull request checkout fails if the git fetch or git checkout operations do not succeed, or if the target branch name does not match the required pr-<pr_number> format. The skill reports these errors directly.

What's the best way to automate jumping into a specific PR branch for testing?

Automating the jump to a specific PR branch for testing requires passing the pull request number. The skill fetches the PR from origin and checks out the branch, enabling rapid context switching for demonstrations.