github-pr

Create GitHub pull requests from feature branches and report preview deployment URLs.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill github-pr-mkrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/github-pr
Command: npx skills add https://github.com/mkrlabs/specflow --skill github-pr-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the repetitive, error-prone process of opening a GitHub Pull Request from a feature branch, triggering CI checks, and reporting a live deployment preview and resource summary.

Core Features & Use Cases

  • Create a GitHub Pull Request from the current feature branch using the gh CLI with a structured PR body.
  • Wait for CI checks to complete and surface the status in the PR context.
  • Retrieve and report the preview deployment URL and a summary of provisioned GCP resources for quick verification.
  • Use when collaborating on feature branches, requesting early feedback, or automating standard PR workflows with preview environments.

Quick Start

Create a PR from the current feature branch and wait for CI plus a preview deployment, then report the preview URL.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with a preview deployment?

Automating GitHub pull request creation and preview deployments requires using the gh CLI to push a feature branch, open a PR with a structured body, and report the live preview URL. This workflow also tracks CI check status before surfacing the deployment link for stakeholder review.

Can I use the gh CLI to wait for CI checks before reporting a PR preview URL?

Yes, the workflow uses the gh CLI to create the PR, trigger CI checks, and wait for them to complete. It then retrieves and reports the preview deployment URL alongside a summary of provisioned resources for quick verification.

How does branch validation work when automating a pull request?

Branch validation ensures you are not creating a pull request from the main branch. The workflow checks that the current feature branch is pushed to the remote repository before proceeding with PR creation and preview deployment generation.

What is the best way to generate a structured PR body for a feature branch?

Generating a structured PR body for a feature branch is handled automatically during PR creation. It includes resource references and context for stakeholder review, ensuring the pull request has a consistent format when deployed to the preview environment.

Do I need to push my feature branch before opening a GitHub pull request?

Yes, you must push your feature branch to the remote repository before opening a GitHub pull request. The workflow validates that the branch is pushed and is not the main branch before automating PR creation and triggering the preview deployment.

When should I use an automated pull request workflow instead of manual creation?

You should use an automated pull request workflow when collaborating on feature branches, requesting early feedback, or needing standard PR workflows with preview environments. It eliminates repetitive manual steps by automating PR creation, CI monitoring, and deployment reporting.