commit-push-pr

Name: commit-push-pr
Availability: InStock
Author: Paulund

Automate Git commits, pushes, and pull request creation from a new branch.

Updated Aug 27, 2026

Search Tags:#git #version control #pull request #workflow automation #commit #push

Ready to run

npx skills add https://github.com/paulund/ai --skill commit-push-pr-paulund

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/paulund/ai/tree/main/git/skills/commit-push-pr
Command: npx skills add https://github.com/paulund/ai --skill commit-push-pr-paulund

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the Git workflow by automating the process of committing changes, pushing them to a remote repository, and opening a pull request, saving developers time and reducing manual steps.

Core Features & Use Cases

Atomic Workflow: Executes branching, committing, pushing, and pull request creation as a single, cohesive operation.
Safety First: Prevents direct commits to the main branch and ensures all steps are completed in the correct order.
Use Case: After making several related changes, you can use this Skill to quickly commit them, push the new branch, and initiate a pull request for review without manually running multiple Git commands.

Quick Start

Use the commit-push-pr skill to commit staged changes, push the current branch, and open a pull request.

Frequently Asked Questions about commit-push-pr

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

FAQPage Schema

How do I automate committing changes, pushing a branch, and opening a pull request in one step?▼

You can automate this Git workflow by using a skill that executes branching, committing, pushing, and pull request creation as a single cohesive operation. It ensures a new branch is created from main before committing and applies conventional commit messaging to streamline the process.

What is the best way to streamline Git workflows for feature development and bug fixing?▼

Streamlining Git workflows for feature development and bug fixing is achieved by automating the sequence of committing changes, pushing them to a remote repository, and opening a pull request. This saves time and reduces manual steps by handling the operations atomically.

Can I commit directly to the main branch when automating a push and pull request?▼

Committing directly to the main branch is prevented by this workflow automation. It enforces a safety-first approach by ensuring a new branch is created from main before committing changes, keeping the main branch protected from direct modifications.

Does this automated Git workflow support unstaged changes or only staged changes?▼

This Git workflow supports both staged and unstaged changes. It automates the process of committing your current modifications, pushing the branch to origin, and initiating a pull request for review without requiring manual staging commands.

How does conventional commit messaging work when automating a pull request?▼

Conventional commit messaging is automatically applied when the workflow commits your changes. It ensures your commit messages follow standard conventions before pushing the branch to origin and opening a pull request for review.

When should I not use an atomic commit, push, and pull request workflow?▼

You should not use this atomic workflow if you need to split unrelated changes into multiple separate commits or pull requests. It is designed for several related changes, handling branching, committing, pushing, and pull request creation as a single operation.