skills.rest
KosmoCHE
KosmoCHECOMMUNITY
Explore all skills by this author →
WebsiteGitHub

push-pr

Create branches, push commits, and open pull requests via gh.

Updated Aug 23, 2026
Search Tags:#automation#git#branch-management#pull-request#conventional-commits#gh-cli
One-click install
npx skills add https://github.com/KosmoCHE/claude-plugins --skill push-pr-kosmoche
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push-pr
Source: https://github.com/KosmoCHE/claude-plugins/tree/main/git-command/skills/push-pr
Command: npx skills add https://github.com/KosmoCHE/claude-plugins --skill push-pr-kosmoche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of creating a feature branch, committing changes with conventional commits, pushing to the remote, and opening a pull request, reducing manual steps and ensuring consistency.

Core Features & Use Cases

  • Branch automation: generate a properly named branch and perform the full PR workflow.
  • Commit discipline: enforce conventional commits in messages.
  • PR creation: automatically open a pull request with relevant metadata.

Quick Start

Create a new branch from the current context, commit changes using conventional commits, push to origin, and open a PR.

Frequently Asked Questions about push-pr

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

FAQPage Schema
How do I automate creating a branch, committing, and opening a pull request?▼

Automating a pull request workflow involves generating a feature branch, enforcing conventional commits, pushing to origin, and using gh pr create to open the PR. This eliminates manual steps and ensures branch naming consistency.

What is a conventional commit and how does it work with branch automation?▼

A conventional commit is a standardized message format enforced during branch automation. It structures commit metadata to clearly indicate feature, bugfix, or release cycles, ensuring consistent Git history before pushing and opening a pull request.

How do I create a pull request using the gh CLI for a feature branch?▼

Creating a pull request via gh CLI requires committing changes to a properly named branch, pushing it to the remote repository, and executing gh pr create. This automatically opens the PR with relevant metadata and clear failure feedback.

Can I use automated branch management for both feature and release cycles?▼

Automated branch management handles both individual developer and team workflows across feature, bugfix, or release cycles. It applies branch naming conventions and conventional commits uniformly to maintain repository consistency before PR creation.

What happens when a pull request creation fails during Git automation?▼

When pull request creation fails during Git automation, the process provides clear failure feedback. This ensures you can quickly identify whether the issue stems from branch naming, commit format, or the gh pr create execution step.

Related Skills

Explore More Software Engineering Skills→
rnbenrnben

github-code-review

Analyze git diffs and generate inline comments for PRs and pre-push checks.

Community
Advanced
ClyptAIClyptAI

ship

Automate release flow by merging branches, running tests, bumping versions, and creating pull requests.

Official
Advanced
carrot-foundationcarrot-foundation
1

rule-commit

Enforces conventional commits with schema-specific scopes via commitlint and Husky.

Official
Basic
kolbickkolbick

prepare-pr

Rebase GitHub Pull Requests onto main and push fixes.

Community
Advanced