pr-workflow

Create GitHub pull requests with titles, descriptions, labels, and reviewers.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill pr-workflow-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/github/pr-workflow
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill pr-workflow-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of pull requests by ensuring they are well-documented, properly formatted, and include all necessary information for reviewers, reducing ambiguity and speeding up the review process.

Core Features & Use Cases

  • Guided PR Creation: Walks users through titling, describing, labeling, and assigning reviewers to pull requests.
  • Standardized Descriptions: Enforces a consistent structure for PR descriptions, including summary, motivation, testing plan, and reviewer notes.
  • Use Case: A developer finishes a new feature and needs to create a pull request. This Skill helps them craft a clear title, write a detailed description explaining the changes and how to test them, and assign the appropriate team members for review.

Quick Start

Use the pr-workflow skill to create a pull request for the current branch with a title 'feat: add user authentication' and a description explaining the changes.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I create a pull request with a complete description and proper labels on GitHub?

To create a pull request with complete details, you can use a guided workflow that automates titling, enforces standardized descriptions, applies relevant labels, and assigns reviewers on GitHub.

What should be included in a GitHub pull request description for a clear code review?

A GitHub pull request description should include a summary, motivation, testing plan, and reviewer notes to ensure clear communication and provide necessary context for an efficient code review process.

How do I automate assigning reviewers and adding labels when creating a pull request?

You can automate assigning reviewers and adding labels by using developer tools that integrate with GitHub to process your branch changes and systematically populate these fields during pull request creation.

Do I need the GitHub CLI installed to automate pull request creation workflows?

Yes, you need the GitHub CLI (`gh`) installed, as the workflow relies on it to interact with your repository, automate pull request creation, and apply formatting best practices for Git commits.

What is the best way to ensure consistent Git commit messages and PR formatting across a development team?

The best way to ensure consistent PR formatting and Git commit messages is to use an automated workflow that enforces a standardized structure for titles, descriptions, and reviewer assignments for every pull request.

Why does my pull request lack proper reviewer notes and a testing plan for code review?

Your pull request lacks these elements because it was created without a standardized template; using a guided PR creation workflow enforces including a testing plan and reviewer notes to reduce ambiguity.