skills.rest
dtbuchholz
dtbuchholzCOMMUNITY
Explore all skills by this author →
Website𝕏@dtbuchholzGitHub

commit-push-pr

Stage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.

Updated Jan 22, 2026
Search Tags:#git#pull request#commit#conventional commits#push#github cli
One-click install
npx skills add https://github.com/dtbuchholz/claude-config --skill commit-push-pr-dtbuchholz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/dtbuchholz/claude-config/tree/main/skills/commit-push-pr
Command: npx skills add https://github.com/dtbuchholz/claude-config --skill commit-push-pr-dtbuchholz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the Git workflow by automating the process of staging changes, creating conventional commits, pushing to a remote repository, and opening a pull request.

Core Features & Use Cases

  • Automated Git Workflow: Handles the entire commit-to-PR cycle with a single command.
  • Conventional Commits: Enforces a standardized commit message format for better project history.
  • Use Case: After completing a new feature, you can use this Skill to quickly commit your changes, push them to your feature branch, and open a pull request for review without manually typing multiple Git commands.

Quick Start

Use the commit-push-pr skill to stage all changes, commit them with a 'feat:' prefix, push to origin, and create 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 git commit, push, and pull request creation in one step?▼

You can automate the entire git workflow by staging changes, creating conventional commits, pushing branches to a remote repository, and opening pull requests via the GitHub CLI in a single command.

What is the conventional commits format and how is it applied during a git push?▼

Conventional commits use standardized prefixes like 'feat:' to structure project history. This format is automatically applied to your commit messages before pushing branches to a remote repository.

Can I use GitHub CLI to create a pull request after committing and pushing a branch?▼

Yes, GitHub CLI is used to open pull requests after staging changes, formatting conventional commits, and pushing branches to a remote repository for collaborative code integration.

Does this automated git workflow support branch protection and atomic commits?▼

Yes, the automated git workflow satisfies requirements for atomic commits and branch protection while streamlining version control management and collaborative code review initiation.

What is the best way to streamline code review initiation for a new feature branch?▼

The best way to streamline code review initiation is to automate staging changes, enforce conventional commits, push to your remote feature branch, and open a pull request automatically.

Do I need to install GitHub CLI separately to open pull requests with this workflow?▼

Yes, GitHub CLI is required to open pull requests automatically after staging changes, creating conventional commits, and pushing branches to a remote repository.

Related Skills

Explore More Software Engineering Skills→
inspedralbesinspedralbes

speckit-git-remote

Detect Git remote URLs and extract owner and repository names.

Official
Intermediate
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
mpazarynampazaryna
1

push

Stage, commit, and push Git changes with conventional commit messages.

Community
Intermediate
auxi-wardrobeauxi-wardrobe
1

ck:git

Automate Git staging, committing, pushing, and pull requests with conventional commits and security scans.

Official
Advanced