commit-push-pr

Commit local changes, push to remote, and create a GitHub pull request.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/drillan/mixseek-plus --skill commit-push-pr-drillan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/drillan/mixseek-plus/tree/main/.claude/skills/commit-push-pr
Command: npx skills add https://github.com/drillan/mixseek-plus --skill commit-push-pr-drillan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive friction of turning finished local changes into a shared GitHub pull request, especially when you need branch handling, commit creation, and remote publishing done reliably.

Core Features & Use Cases

  • End-to-End Git Workflow: Handles commit creation, push operations, and PR creation as a single coordinated process.
  • Branch and PR Management: Detects the repository’s default branch, checks whether a PR already exists, and avoids duplicate PR creation.
  • Quality Gate Integration: Verifies workflow quality checks before creating a PR when the repository’s configuration requires it.
  • Use Case: A developer finishes a feature, invokes this Skill, and gets a clean commit pushed to the correct branch with a linked pull request ready for review.

Quick Start

Use this Skill when you want your current changes committed, pushed, and turned into a pull request with the appropriate checks and branch handling applied automatically.

Frequently Asked Questions about commit-push-pr

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

FAQPage Schema
How do I commit, push, and create a GitHub pull request in one workflow?

You can automate the end-to-end git workflow by using a tool that commits local changes, pushes them to the remote repository, and creates a GitHub pull request in a single coordinated process. This eliminates the repetitive friction of manual branch management and PR creation.

Can I automatically check for existing pull requests to avoid duplicates?

Yes, you can automatically check for existing pull requests to avoid duplicates by using a workflow that detects the repository's default branch and verifies whether a PR already exists. This prevents duplicate PR creation and ensures safe branch management.

Do I need GitHub CLI access to automate commit and push workflows?

Yes, GitHub CLI access is required to automate commit and push workflows that create pull requests. The CLI provides the necessary remote repository authentication, default-branch detection, and workflow quality-gate validation to safely complete the PR creation process.

How do workflow quality gates integrate with pull request creation?

Workflow quality gates integrate with pull request creation by verifying repository configuration checks before opening a PR. This validation ensures that required tests pass and code quality standards are met, preventing broken commits from being pushed for review.

What is the best way to handle branch management for feature delivery?

The best way to handle branch management for feature delivery is to use a coordinated workflow that detects the repository's default branch, commits changes, and pushes to the correct remote branch automatically. This ensures proper issue linkage and clean developer handoff.

Why does my automated pull request workflow fail on quality checks?

An automated pull request workflow may fail on quality checks when the repository's configuration requires validation gates that are not met before PR creation. The workflow intentionally blocks the process to prevent pushing commits that do not satisfy required testing standards.