create-pr

Name: create-pr
Availability: InStock
Author: abretonc7s

Create draft GitHub pull requests with validation and review assignment.

Updated Apr 10, 2026

Search Tags:#automation #devops #code review #pull request #github #ci

Ready to run

npx skills add https://github.com/abretonc7s/metamask-skills --skill create-pr-abretonc7s

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/abretonc7s/metamask-skills/tree/main/domains/pr-workflow/skills/create-pr
Command: npx skills add https://github.com/abretonc7s/metamask-skills --skill create-pr-abretonc7s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the full process of creating and managing GitHub pull requests to improve development workflow efficiency.

Core Features & Use Cases

Precondition Checks: Validates current Git branch status and ensures a clean working directory before initiating a PR.
PR Generation: Automates the creation of draft pull requests with autogenerated titles and descriptions via CLI or API.
Code Owner Identification: Finds relevant code owners and Slack handles for changed files to streamline review assignment.
Review Outreach: Sends review requests and prompts team members for feedback within designated channels.
Use Case: A developer finishes code on a feature branch, runs this skill to automatically create a PR, notify the right reviewers, and prepare review messages.

Quick Start

Run the create-pr skill to generate a draft pull request for your current branch targeting the main branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate GitHub pull request creation from a local branch?▼

Automating GitHub pull request creation involves validating your local Git branch status and clean working directory, then using CLI or API tools to generate a draft PR with autogenerated titles and descriptions.

What is the best way to assign code owners for pull request reviews automatically?▼

Automatically assigning code owners for pull request reviews requires detecting changed files in your repository structure to identify relevant reviewers and their Slack handles for targeted review outreach.

Can I use GitHub CLI to validate preconditions before creating a pull request?▼

Yes, GitHub CLI can validate preconditions by checking your current Git branch status and ensuring a clean working directory before initiating the automated pull request generation process.

How do I send review requests and notify team members after creating a pull request?▼

Sending review requests after pull request creation involves prompting team members for feedback within designated channels by routing review outreach messages to the identified code owners.

Do I need GitHub API tools and knowledge of code repository structure to automate PR workflows?▼

Yes, automating PR workflows requires GitHub CLI or API tools and knowledge of your code repository structure to accurately detect code owners and ensure consistent pull request generation across multiple development projects.

Why does pull request automation fail when my working directory is not clean?▼

Pull request automation fails with an unclean working directory because precondition checks validate local Git branch status to ensure a clean state before initiating the draft PR generation workflow.