commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/VYRE-Studios/Windows-Agentic-Framework --skill commit-push-pr-vyre-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/VYRE-Studios/Windows-Agentic-Framework/tree/main/skills/claude-code/commit-push-pr
Command: npx skills add https://github.com/VYRE-Studios/Windows-Agentic-Framework --skill commit-push-pr-vyre-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often have to manually run multiple git commands to commit changes, push a branch, and create a pull request, which is time‑consuming and error‑prone.

Core Features & Use Cases

  • Automated Commit: Stages specified files and creates a clear, structured commit message.
  • Branch Validation & Push: Checks branch tracking, ensures the branch is ready, and pushes it with proper upstream configuration.
  • Pull Request Creation: Generates a well‑formatted PR title and body using the GitHub CLI, adhering to best‑practice guidelines.
  • Use Case: After completing a feature, run this skill to instantly prepare the commit, push the branch, and open a PR for review without leaving the terminal.

Quick Start

Use the commit-push-pr skill to automatically commit your changes, push the branch, and open a pull request with a formatted title and description.

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 git commit, push, and pull request creation in one step?

Automating git commit, push, and pull request creation requires a Skill that stages files, pushes the branch with upstream configuration, and opens a GitHub PR via the CLI, consolidating manual commands into a single workflow.

What is the best way to open a GitHub pull request after pushing a branch?

The best way to open a GitHub pull request after pushing is using a tool that automatically generates a well-formatted PR title and body via the GitHub CLI, ensuring structured documentation for code review.

Do I need the GitHub CLI to automate pull request creation from the terminal?

Yes, you need the GitHub CLI installed to automate pull request creation from the terminal, as it handles branch validation, upstream configuration, and the PR generation process.

Can I use commit-push-pr to validate branch tracking before pushing to a remote repository?

Yes, you can use it to validate branch tracking before pushing to a remote repository, as it checks branch readiness and applies proper upstream configuration during the push.

Why does automating git commands reduce errors in software development workflows?

Automating git commands reduces errors in software development workflows by replacing manual command execution for commits, pushes, and PR creation with a standardized, repeatable process.

Does this automated commit and push workflow work without appropriate repository permissions?

No, this automated commit and push workflow requires appropriate repository permissions to create commits and pull requests, alongside a git-enabled project directory.