commit-to-pr

Create a single conventional commit and GitHub PR from local changes.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill commit-to-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-to-pr
Source: https://github.com/japurcell/skills/tree/main/skills/commit-to-pr
Command: npx skills add https://github.com/japurcell/skills --skill commit-to-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning scattered local changes into a clean, reviewable pull request by automating branch creation, commit messaging, and PR generation.

Core Features & Use Cases

  • Stage all changes, select or create a feature branch, and enforce a single, atomic commit.
  • Attach issue links to the commit and PR body to streamline traceability.
  • Push to origin and open a PR with gh pr create in a non-interactive workflow.

Quick Start

Run the commit-to-pr workflow on your current workspace to create a feature branch, make one conventional commit linked to issues, push, and open a PR.

Frequently Asked Questions about commit-to-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 commits?▼

Automating a GitHub pull request from local commits involves staging changes, creating a feature branch, pushing to origin, and running gh pr create non-interactively to open a reviewable PR.

How do I link GitHub issues to a commit and pull request automatically?▼

Linking GitHub issues to a commit and pull request uses issue numbers as input to automatically attach issue references to both the single atomic commit message and the PR body for traceability.

Can I create a feature branch and make a single conventional commit in one workflow?▼

Yes, you can create a feature branch and make a single conventional commit in one workflow by staging all local changes, selecting or creating the branch, and enforcing one atomic commit before pushing.

Do I need the GitHub CLI to create a pull request non-interactively?▼

Creating a pull request non-interactively requires the GitHub CLI, specifically the gh pr create command, to push staged local changes to origin and open the PR without manual intervention.

What is the best way to convert scattered local changes into a reviewable PR?▼

Converting scattered local changes into a reviewable PR is best handled by automating branch creation, combining all modifications into a single conventional commit with a Co-authored-by trailer, and generating the PR.

Can I override the base branch when creating a pull request from local changes?▼

Yes, you can override the base branch when creating a pull request; the workflow defaults to main but accepts a feature branch override to target a different base branch for the PR.