skills.rest
Palbahngmiyine
PalbahngmiyineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fork-pr

Create pull requests from forked repositories to upstream using gh CLI.

Updated Mar 10, 2026
Search Tags:#automation#git#pull-request#upstream#fork#commit-analysis
One-click install
npx skills add https://github.com/Palbahngmiyine/harness --skill fork-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork-pr
Source: https://github.com/Palbahngmiyine/harness/tree/main/skills/fork-pr
Command: npx skills add https://github.com/Palbahngmiyine/harness --skill fork-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forked repositories often struggle to generate consistent PRs to upstreams; this skill automates PR creation by analyzing git history and summarizing commits into a coherent PR description.

Core Features & Use Cases

  • Analyze commit history from a fork and determine changes to propose to the upstream.
  • Auto-generate PR title and body based on Conventional Commits and detected changes.
  • Validate remote configuration and optionally prompt to run tests/build before submission in a controlled workflow.

Quick Start

Run the fork-pr command to create a PR from your fork to the upstream repository.

Frequently Asked Questions about fork-pr

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

FAQPage Schema
How do I automatically create a pull request from a fork to the upstream repository?▼

To automatically create a pull request from a fork to the upstream repository, you can use a skill that analyzes your commit history and summarizes changes into a structured PR title and body using the gh CLI.

How do I generate a pull request description from my git commit history?▼

Generating a pull request description from your git commit history is done by analyzing your commits, validating conventional commit formats, and summarizing the detected changes into a coherent PR body.

Do I need to configure git remotes before generating an upstream PR from a fork?▼

Yes, you need to configure git remotes before generating an upstream PR from a fork, specifically setting up origin for your fork and upstream for the source repository to validate and route the pull request correctly.

Can I run tests before submitting a pull request to the upstream repository?▼

Yes, you can optionally prompt to run tests or builds before submitting a pull request to the upstream repository, enabling a controlled workflow that validates your changes via the gh CLI prior to final creation.

What is the best way to manage conventional commits when submitting upstream PRs?▼

The best way to manage conventional commits when submitting upstream PRs is to use an automation tool that validates your commit history and auto-generates the PR title and body based on the detected conventional commit changes.

Related Skills

Explore More Software Engineering Skills→
sluongngsluongng
6

buck2-stack-maintainer

Rebase fork/stack onto origin/main and publish merge commits to fork/main.

Community
Advanced
furrycolombia-sysfurrycolombia-sys
1

review-branch

Identify and patch discrepancies between the current branch and develop.

Community
Intermediate
HorusGoulHorusGoul
8

land

Merge pull requests by resolving conflicts, checking CI/CD, and squashing via GitHub API.

Community
Advanced
adrhilladrhill
40

pr

Create GitHub pull requests with Conventional Commits titles and bodies.

Community
Intermediate