github-pr

Fetch, preview, merge, and test GitHub pull requests locally.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Lutra23/content-workflow --skill github-pr-lutra23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/Lutra23/content-workflow/tree/main/skills/github-pr
Command: npx skills add https://github.com/Lutra23/content-workflow --skill github-pr-lutra23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, typer, and includes scripts (resource) components.

What problem does it solve?

GitHub PR Tool enables developers to preview, fetch, merge, and test GitHub pull requests locally, reducing integration risk by validating changes before they reach the main branch.

Core Features & Use Cases

  • Preview a PR to see its title, author, status, files changed, and CI status.
  • Fetch the PR head into a local branch for testing and review.
  • Merge the PR into your current branch and optionally install dependencies and run tests.
  • Run a full test cycle, including dependency installation and verification of build status.

Quick Start

Preview a PR from a repository to inspect its details before merging.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I preview a GitHub pull request locally before merging?

To preview a GitHub pull request locally, you can fetch the PR branch to inspect its title, author, status, files changed, and CI status. This allows you to review upstream changes and verify cross-repo compatibility before integration.

Can I automatically run tests after merging a pull request branch?

Yes, you can merge a pull request into your current branch and optionally install dependencies to run a full test cycle. This verifies the build status and validates changes before they reach the main branch.

What's the best way to test GitHub PRs from forks in a local development environment?

The best way to test GitHub PRs from forks locally is to fetch the PR head into a local branch. This allows you to manage forks, preview details, merge with optional installs, and run tests to reduce integration risk.

Do I need any specific Python packages to fetch and test GitHub PRs locally?

Yes, you need the Python packages rich and typer to run this GitHub PR workflow. These dependencies support the scripts that fetch, preview, merge, and test pull requests in your local environment.

Why validate GitHub pull requests locally instead of relying on CI status?

Validating GitHub pull requests locally reduces integration risk by allowing you to run a full test cycle and verify cross-repo compatibility. Previewing files and CI status locally ensures changes are safe before reaching the main branch.

What details can I see when previewing a GitHub pull request?

When previewing a GitHub pull request, you can see the title, author, status, files changed, and CI status. Fetching the PR head into a local branch lets you review these details before merging.