skills.rest
skaisser
skaisserCOMMUNITY
Explore all skills by this author →
Website𝕏@smkaisserGitHub

pr

Create pull requests with plan context and GitHub issue references.

4|Updated Mar 24, 2026
Search Tags:#automation#workflow#github#pr#pull-request#base-branch#plan-context
One-click install
npx skills add https://github.com/skaisser/blueprint --skill pr-skaisser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/skaisser/blueprint/tree/main/skills/pr
Command: npx skills add https://github.com/skaisser/blueprint --skill pr-skaisser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating pull requests with plan context and correct base branches can be error-prone and slow. This Skill ensures PRs are generated from the right branch, with proper context and GitHub issues integration.

Core Features & Use Cases

  • Automatic base-branch detection ensuring PRs target staging or main as appropriate.
  • Plan-context propagation into the PR and references to related GitHub issues.
  • Enforcement of the ship-before-PR requirement and structured PR details.

Quick Start

Create a PR for the current feature branch using the plan context.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a pull request with plan context on GitHub?▼

To create a pull request with plan context, the Skill propagates your plan details into the PR description and automatically extracts related GitHub issue references. It ensures the PR is generated from the correct feature branch with structured formatting.

How does base-branch detection work for pull requests?▼

Base-branch detection determines the correct target branch for your pull request through your configured workflow. It automatically identifies whether to target staging or main, preventing errors when creating PRs across different branch flows.

How do I link GitHub issues to a pull request automatically?▼

Linking GitHub issues happens automatically by extracting issue references from your plan context. The Skill parses the plan details and embeds the related issue references directly into the formatted PR description.

Do I need to run /ship before creating a pull request?▼

Yes, you must run /ship before creating a pull request. The Skill enforces the ship-before-PR requirement, ensuring the workflow completes the necessary shipping steps before generating the PR with its plan context and issue references.

What is the best way to format PR descriptions across different workflows?▼

The best way to format PR descriptions across workflows is using automated PR generation with plan context. This ensures consistent formatting, correct base-branch targeting, and proper integration of GitHub issues without manual entry.

Can I use this PR automation for branches without an existing plan?▼

No, this PR automation requires existing plan context to function correctly. The Skill extracts issue references and generates the structured PR description directly from the plan, so a branch without a plan cannot provide the necessary context.

Related Skills

Explore More Software Engineering Skills→
CenredJunCenredJun

finishing-a-development-branch

Performs checkout of requested branch or tag with customizable options.

Community
Intermediate
Jia-Hong-PengJia-Hong-Peng

land-and-deploy

Merges pull requests and verifies production canary health after CI/CD deployment completes.

Community
Advanced
DYAI2025DYAI2025
3

finishing-a-development-branch

Verify tests and execute merge, PR, keep, or cleanup workflows for a development branch.

Community
Intermediate
shidax-corpshidax-corp

Create GitHub Issues and Pull Requests

Create and manage GitHub Issues and Pull Requests via the GitHub CLI.

Official
Intermediate