commit-push-pr

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

Automate committing changes, pushing to a feature branch, and creating a pull request.

3|1|Updated Jan 14, 2026

Search Tags:#automation #git #workflow #commit #branch #gh #pull-request

Ready to run

npx skills add https://github.com/heyAyushh/stacc --skill commit-push-pr-heyayushh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/heyAyushh/stacc/tree/main/configs/commands/skills/commit-push-pr
Command: npx skills add https://github.com/heyAyushh/stacc --skill commit-push-pr-heyayushh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams waste time performing repetitive git operations to commit changes, push to a remote branch, and open pull requests. This Skill automates that workflow end-to-end to reduce manual steps and ensure consistency.

Core Features & Use Cases

One-shot workflow that commits changes, pushes to the current branch, and opens a PR.
Pre-checks to discourage direct pushes to main/master and to validate remote origin availability.
Simple template guidance for PR titles and bodies to improve code review consistency.

Quick Start

Open a feature branch, make changes, and run commit-push-pr to automatically create a PR on GitHub with a standardized title and body.

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, pushing, and creating a pull request in one step?▼

You can automate the git workflow by running a single command that commits changes, pushes to your current feature branch, and opens a GitHub pull request. This eliminates repetitive manual git operations and ensures standardized PR creation.

Does this workflow prevent direct pushes to the main branch?▼

Yes, the workflow includes pre-checks that discourage direct pushes to main or master. It validates your current branch against main and checks remote origin availability to enforce branch protection before committing and pushing.

Can I use this to standardize pull request titles and bodies for code review?▼

Yes, the workflow provides simple template guidance for PR titles and bodies. This improves code review consistency across software development teams by standardizing the format of pull requests created on GitHub.

Do I need GitHub authentication and a remote named origin to push and create PRs?▼

Yes, you need GitHub authentication and a remote named origin configured. The workflow uses git and gh commands to push changes and create pull requests, relying on these prerequisites to function correctly.

What is the best way to handle incremental feature branch work across multiple repositories?▼

Automating the end-to-end git workflow handles incremental feature branch work across multiple repositories. It commits changes, pushes to the remote branch, and opens a standardized pull request in one go, ensuring consistency for development teams.