pr

Create a pull request from a local branch using git and GitHub CLI.

9|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/0xrafasec/ai-workflow --skill pr-0xrafasec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/0xrafasec/ai-workflow/tree/main/skills/pr
Command: npx skills add https://github.com/0xrafasec/ai-workflow --skill pr-0xrafasec

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of opening a pull request for code reviews, ensuring that branches are ready for review without manual intervention.

Core Features & Use Cases

  • Automated PR Creation: Automatically opens a pull request with the current branch's commits.
  • Branch Validation: Checks for clean branches and adheres to trunk-based workflow conventions.
  • Draft PR Support: Option to open a pull request as a draft for work-in-progress reviews.

Quick Start

Open a pull request for your current branch by using the command: /pr

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation from a local branch?

You can automate pull request creation by running the /pr command, which validates your branch name, checks for uncommitted changes, ensures commits are on the main branch, and opens the PR for code review.

Do I need GitHub CLI installed to open a pull request with this automation?

Yes, you need both git and the GitHub CLI (gh) installed in your environment, as the GitHub CLI is required to automatically create the pull request from your local branch.

Can I open a draft pull request for work-in-progress code?

Yes, you can open a draft pull request for work-in-progress code. The automation provides an option to open the PR as a draft, allowing reviewers to see your changes before they are finalized.

What branch validations are checked before opening a GitHub pull request?

Before opening a GitHub pull request, the automation validates the branch name, checks for uncommitted changes to ensure a clean branch, and verifies that your commits are on the main branch.

Does this PR automation support trunk-based development workflows?

Yes, the PR automation adheres to trunk-based workflow conventions by validating branch names and ensuring your local commits are properly based on the main branch before opening a pull request.