git-create-pr

Automate commit, push, and pull request creation for Git repositories.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill git-create-pr-3balljuggleryu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-create-pr
Source: https://github.com/3balljugglerYu/ai_coordinate/tree/main/.agents/skills/git-create-pr
Command: npx skills add https://github.com/3balljugglerYu/ai_coordinate --skill git-create-pr-3balljuggleryu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating pull requests by automating commits, pushes, and PR generation with built-in safety rules.

Core Features & Use Cases

  • Automated Workflow: Executes commit -> push -> PR creation in a single step.
  • Safety Features: Enforces branch protection rules and prevents direct pushes to main branches.
  • Conventional Commits: Recommends and applies commit messages in the Conventional Commits format.
  • PR Template Integration: Utilizes existing PR templates or falls back to gh pr create --fill.
  • Use Case: After finishing a feature, you can invoke this skill to commit your changes, push them to a new branch, and open a pull request, all while ensuring best practices are followed.

Quick Start

Use the git-create-pr skill to create a pull request for your current changes.

Frequently Asked Questions about git-create-pr

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

FAQPage Schema
How do I automate creating a pull request after committing changes?

Automating pull request creation executes the commit, push, and PR generation steps in a single workflow. This process integrates with existing PR templates or falls back to standard command line fill defaults to open the request efficiently.

What is the best way to enforce conventional commits when pushing to GitHub?

Enforcing conventional commits during a push is handled by recommending and applying standardized commit message formats automatically. This ensures your Git history follows consistent conventions before the branch is pushed and a pull request is opened.

How do I prevent direct pushes to main branches when automating Git workflows?

Preventing direct pushes to main branches is achieved through built-in safety rules that enforce branch protection. The automation checks protected branch status before committing, ensuring changes are routed through a new branch and pull request instead.

Can I use existing PR templates with automated GitHub pull request generation?

Existing PR templates can be used with automated GitHub pull request generation. The workflow integrates with your repository's predefined templates to populate the PR body, falling back to standard fill commands if no template is found.

Does automated pull request creation work without external dependencies?

Automated pull request creation works without external dependencies, relying solely on standard Git and GitHub command line tools. It uses native CLI commands to push branches and create requests, requiring no additional package installations.

Why should I use an automated workflow for Git pull requests instead of manual commands?

Using an automated workflow for Git pull requests eliminates manual command sequencing errors by chaining commit, push, and creation steps together. It enforces branch protection and conventional commit standards natively, resulting in safer and more consistent repository updates.