agent-create-pr

Automate staging, branching, committing, pushing, and GitHub PR creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow eliminates manual steps in preparing and submitting code changes by automating staging, branching, committing, pushing, and opening a GitHub pull request.

Core Features & Use Cases

  • Stage changes with git, warn on sensitive paths, and ensure there are commits to push
  • Automatically branch on main/master when appropriate and derive descriptive branch names
  • Commit staged changes with meaningful messages derived from inputs or diffs
  • Push to origin and create a PR with a detailed title and body for review
  • Output the PR URL and a summary of actions taken after completion

Quick Start

Run the PR automation on your current branch to stage changes, create a feature branch if needed, commit, push, and open a GitHub pull request.

Frequently Asked Questions about agent-create-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 changes?

Automate creating a GitHub pull request by staging changes, branching from main when needed, deriving commit messages, pushing to origin, and running gh pr create with generated titles and bodies.

What is the best way to automate git branch management and PR generation?

Automating git branch management and PR generation involves detecting when you are on main or master, automatically creating a descriptive feature branch, committing staged files, and opening a pull request on GitHub.

How does commit message derivation work when automating pull requests?

Commit message derivation works by analyzing your inputs or git diffs to generate meaningful messages, which are then used for both the commit and the pull request title and body.

Can I use this to automate staging and pushing code without manual git commands?

Yes, this workflow handles staging changes, warns on sensitive paths, ensures there are commits to push, and pushes to origin automatically, eliminating manual git commands for pull request preparation.

Does this PR automation workflow require any external dependencies?

This PR automation workflow requires no external dependencies, relying solely on git and GitHub CLI (gh) functionality to manage branches, commits, pushes, and pull request creation.

What happens if I run PR automation while on the main branch?

When running PR automation on the main or master branch, it automatically creates a new feature branch with a descriptive name before committing and pushing your changes to ensure proper branch handling.