create-pr

Create pull requests from local code changes and return the PR URL.

9.0k|629|Updated Apr 16, 2025
One-click install
npx skills add https://github.com/mengxi-ream/read-frog --skill create-pr-mengxi-ream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/mengxi-ream/read-frog/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/mengxi-ream/read-frog --skill create-pr-mengxi-ream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of pull requests from local code changes, reducing manual steps and ensuring consistency across PRs.

Core Features & Use Cases

  • Automates branch creation, commit readiness checks, and PR submission to the remote repository.
  • Supports optional binding to an issue number and enforces a structured changeset workflow.
  • Provides a guided, end-to-end PR creation workflow from local changes to GitHub, returning the PR URL for easy access.

Quick Start

Create a PR from your current changes and optionally link it to an issue number.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from local code changes?

Automating pull request creation from local code changes involves applying a structured branch and commit workflow, running readiness checks, and submitting the PR via command-line tools to return the remote URL.

What is a changeset workflow and when do I need it for a pull request?

A changeset workflow formalizes local code modifications into structured commits before submission. You need it for a pull request to ensure consistency, guide status checks, and prepare changes for remote repository synchronization.

Can I link a pull request to an issue number automatically?

Yes, you can link a pull request to an issue number automatically. The PR creation workflow supports optional binding to issue numbers, embedding the reference directly during the automated branch submission process.

Does this PR automation workflow require specific git remote setup?

This PR automation workflow requires a configured git remote repository to push branches and submit changes. It relies on standard remote synchronization to process local commits and return the final GitHub PR URL.

What is the best way to formalize local commits into a GitHub PR?

The best way to formalize local commits into a GitHub PR is using an automated workflow that enforces branch creation, suggests changesets, pushes to remote, and submits the pull request to retrieve the accessible URL.