github-pr

Convert local git changes into a GitHub Pull Request with a conventional commit message.

2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/damacus/agent-skills --skill github-pr-damacus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/damacus/agent-skills/tree/main/skills/github-pr
Command: npx skills add https://github.com/damacus/agent-skills --skill github-pr-damacus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning local git changes into a GitHub Pull Request with a consistent conventional commit message, reducing manual steps and review delays.

Core Features & Use Cases

  • Analyze git diff and produce a concise, conventional commit message.
  • Create and switch to a dedicated feature branch from main when needed, then commit and push.
  • Open a PR on GitHub using the gh CLI with a descriptive title and body.

Quick Start

Summarize your current changes, generate a conventional commit, push to a new feature branch, and open a PR on GitHub.

Frequently Asked Questions about github-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 git changes?

Automating a GitHub pull request involves parsing your git diff, generating a conventional commit message, pushing a feature branch to origin, and running gh pr create to open the PR with a descriptive title and body.

How do I generate a conventional commit message from a git diff?

Generating a conventional commit message from a git diff requires analyzing the local changes and summarizing them into a concise, standardized format that clearly describes the modifications before staging and committing.

Do I need the GitHub CLI to open a pull request from a feature branch?

Yes, opening a pull request from a feature branch requires the GitHub CLI to execute gh pr create, which submits the title and body to GitHub after pushing your committed changes to the remote origin.

What's the best way to manage feature branches before opening a GitHub PR?

Managing feature branches before opening a GitHub PR involves creating and switching to a dedicated branch from main, staging your changes, committing them with a conventional message, and pushing to origin.

Can I use this git branch management workflow for solo development on GitHub?

Yes, this git branch management workflow applies to both solo and team development on GitHub repositories, guiding you from initial diff analysis through feature branch creation to final PR submission.