commit-push-pr

Automate commit, push, and pull request creation with CI monitoring.

3|1|Updated Mar 23, 2026

Search Tags:#git #workflow #commit #push #ci #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/malinskibeniamin/skills --skill commit-push-pr-malinskibeniamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/malinskibeniamin/skills/tree/main/commit-push-pr
Command: npx skills add https://github.com/malinskibeniamin/skills --skill commit-push-pr-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An automated, end-to-end workflow that takes code changes from local commits through to an opened pull request, coordinating pre-flight checks, commit categorization, branch handling, and CI monitoring.

Core Features & Use Cases

End-to-end PR automation: orchestrates commit generation, branch creation, push, and PR creation with CI checks.
Conventional-commits & labeling: analyzes changes, assigns conventional commit types, and applies labels in PRs.
Use Case: When a developer asks to merge feature work, run the flow to produce a PR with a clear, categorized commit history and CI visibility.

Quick Start

Run the full commit-push-PR flow on your current changes by invoking the skill in your CLI or IDE integration.

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 workflow?▼

You can automate the commit-push-PR workflow by running a skill that handles pre-flight checks, branch strategy, categorized commits, push, PR creation, and CI watch on the active branch.

How do conventional commits work when automating a pull request?▼

Conventional commits categorize code changes by analyzing the diff and assigning standardized commit types, ensuring a clear commit history before pushing and opening a pull request.

Can I monitor CI checks automatically after opening a pull request?▼

Yes, the automated workflow includes CI monitoring on the active branch, watching continuous integration checks immediately after the pull request is created and pushed.

Do I need the gh CLI to automate opening pull requests from the command line?▼

Yes, you need a Git repository with an authenticated gh CLI and network access to the remote to execute the automated commit-push-PR flow.

Why does the commit-push-PR workflow require a clean working tree?▼

A clean working tree is required because the workflow performs pre-flight checks before orchestrating branch creation, commits, and push operations to prevent conflicts.

What's the best way to handle branch strategy when automating pull requests?▼

The workflow handles branch strategy automatically by orchestrating branch creation alongside commit categorization and push operations during the PR automation flow.