commit-push-pr

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

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/d3ming/dot-agents --skill commit-push-pr-d3ming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/d3ming/dot-agents/tree/main/master/skills-archive/commit-push-pr
Command: npx skills add https://github.com/d3ming/dot-agents --skill commit-push-pr-d3ming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the multi-step Git workflow of reviewing changes, creating or selecting a branch, committing with a clear message, pushing to origin, and opening a pull request so developers can avoid mistakes and save time.

Core Features & Use Cases

  • Change review: Reminds to inspect git status and diffs before committing to avoid accidental inclusions.
  • Branch management: Creates a feature branch when on main/master and uses the current branch otherwise to keep history clean.
  • Safe commits and pushes: Encourages selective staging, Conventional Commit messages, optional use of a committer script, and pushes with upstream tracking.
  • PR creation and tracker linking: Scans commits for tracker references, includes them in the PR body, enforces a structured PR template (Impact / Summary / Test plan), and uses the GitHub CLI to open the PR while enforcing guardrails like no force-push and no direct pushes to main/master.
  • Use Case: A developer finishing a bugfix can run the workflow to produce a vetted commit, push the branch, and create a PR populated with tracker links and the recommended PR body.

Quick Start

Commit your changes, push the feature branch, and open a pull request with a descriptive title and the recommended Impact, Summary, and Test plan sections in the 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 changes, pushing a branch, and opening a pull request?

To automate committing, pushing, and opening a pull request, use this workflow to review diffs, stage selectively, push with upstream tracking, and generate a structured PR body via the GitHub CLI.

Do I need the GitHub CLI installed to create a pull request from the command line?

Yes, the GitHub CLI is required for PR creation within this workflow. It automates opening the pull request and populating the structured template with tracker references found in your commits.

How does this workflow handle committing changes directly on the main branch?

Committing changes directly on main or master is blocked by guardrails. The workflow automatically creates a new feature branch when you are on main/master to keep your Git history clean.

Can I include tracker references automatically when I open a pull request?

Yes, the workflow scans your commits for tracker references and includes them in the PR body. It enforces a structured template with Impact, Summary, and Test plan sections.

What are the limitations of force pushing when using this Git workflow?

The workflow enforces push guardrails that prevent force-pushes and direct pushes to main/master. These limitations ensure safe commits and protect your repository history during feature branch development.

What's the best way to format commit messages before pushing a feature branch?

The best way to format commit messages is using Conventional Commit standards. The workflow encourages selective staging and clear messages before pushing your branch to origin with upstream tracking.