github-pr

Create GitHub pull requests by committing, rebasing, and force-pushing changes.

101|83|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/hw-native-sys/pypto --skill github-pr-hw-native-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/hw-native-sys/pypto/tree/main/.claude/skills/github-pr
Command: npx skills add https://github.com/hw-native-sys/pypto --skill github-pr-hw-native-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating a GitHub pull request after committing, rebasing, and pushing changes, simplifying the code review submission workflow.

Core Features & Use Cases

  • Automated Workflow: Guides users through committing, rebasing, and pushing changes before creating a pull request.
  • Conflict Resolution Assistance: Provides steps for resolving merge conflicts during rebase.
  • Safe Pushing: Emphasizes the use of --force-with-lease for safer force pushes.
  • Use Case: After making several feature updates locally, you want to submit them for review. This skill will ensure your branch is up-to-date with the main branch, push your changes, and open a PR on GitHub.

Quick Start

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

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I automate GitHub pull request creation after rebasing?

Automating GitHub pull request creation involves orchestrating git commands to commit, rebase, and push changes using --force-with-lease. The skill then integrates with GitHub CLI to open a pull request using pre-defined title and body templates.

What is the safest way to force push git commits before opening a PR?

The safest way to force push git commits before opening a PR is using the --force-with-lease flag. This ensures safer force pushing by preventing accidental overwrites of remote changes during your workflow automation.

How do I handle merge conflicts when rebasing before a GitHub pull request?

Handling merge conflicts during a rebase before a GitHub pull request requires resolving the conflicts manually. This skill provides specific steps and guidance for resolving merge conflicts during the rebase process.

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

Yes, you need the GitHub CLI to automate pull request workflows. The skill integrates directly with the GitHub CLI to create the pull request on your behalf using pre-defined title and body templates.

How does workflow automation streamline code review submissions on GitHub?

Workflow automation streamlines code review submissions by orchestrating git commands to ensure your branch is up-to-date with the main branch. It automatically pushes your local feature updates and opens a PR on GitHub for review.