create-pr

Automate GitHub pull request creation with local Git operations and conventional commits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yyiilluu/reflexio --skill create-pr-yyiilluu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/yyiilluu/reflexio/tree/main/.claude/commands/create-pr
Command: npx skills add https://github.com/yyiilluu/reflexio --skill create-pr-yyiilluu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating and submitting pull requests, ensuring code is well-formatted, committed, and pushed with descriptive messages.

Core Features & Use Cases

  • Automated Commit & Push: Stages, lints, formats, and commits changes with conventional commit messages.
  • Branch Management: Creates feature branches and ensures they are up-to-date with the base branch.
  • PR Creation: Generates a well-structured pull request title and body, including summaries, changes, and test plans.
  • Use Case: After making several bug fixes, use this Skill to automatically commit them, create a new branch, push it, and open a pull request for review.

Quick Start

Use the create-pr skill to create a pull request for your current changes.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate creating a GitHub pull request from local code changes?

To automate creating a GitHub pull request, you can use a tool that stages your code changes, generates conventional commit messages, pushes a feature branch, and submits the PR via the GitHub CLI.

Do I need GitHub CLI installed to submit pull requests automatically?

Yes, GitHub CLI is required to submit pull requests automatically, as the tool relies on it to interact directly with the GitHub API for creating branches and opening PRs.

Can I generate conventional commit messages automatically before pushing a feature branch?

Yes, you can generate conventional commit messages automatically by analyzing your code diffs, which ensures your staged changes are committed with standardized, descriptive messages before pushing.

What is the best way to structure a pull request body from a code diff?

The best way to structure a pull request body from a code diff is to automatically generate sections for summaries, detailed changes, and test plans, ensuring well-formatted and descriptive PR submissions.

How does automated branch rebasing work before opening a pull request?

Automated branch rebasing works by checking your feature branch against the base branch, ensuring your local Git operations integrate the latest upstream changes before you push and open a pull request.

Are there limitations to automating Git operations like staging and committing?

A limitation of automating Git operations like staging and committing is that the tool requires a specific environment setup with GitHub CLI and proper local repository access to execute linting, formatting, and rebasing successfully.