commit-push-pr-flow

Commit changes, push to a branch, and open a pull request.

1|1|Updated Nov 27, 2025

Search Tags:#automation #workflow #commit #branching #push #code-review #pull-request

Ready to run

npx skills add https://github.com/HikaruEgashira/agent-skills --skill commit-push-pr-flow

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the post-task workflow by committing changes, pushing to the repository, and opening a pull request, ensuring code is submitted consistently.

Core Features & Use Cases

Create a branch if the current branch is in the default set and open a PR
Follow a PR template and include a description (Japanese: 提出後は gh pr view --web で差分を共有して完了してください)
After completion, invoke the review-flow to continue the workflow

Quick Start

After finishing a task, run this skill to automatically commit, push, and open a PR.

Frequently Asked Questions about commit-push-pr-flow

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 after finishing a coding task?▼

You can automate the post-task code submission workflow by using a tool that commits changes, pushes to a branch, and opens a pull request automatically. This ensures code is submitted consistently without manual intervention.

What is the best way to ensure my pull requests follow a consistent template format?▼

To ensure consistent PR formatting, you can use an automated workflow that applies a predefined PR template and includes a description when opening the pull request. This removes the need to manually format your code review submissions.

How do I automatically create a new branch when committing changes to a default branch?▼

Automated branching workflows can detect if your current branch is in the default set and automatically create a new branch before pushing your changes and opening a pull request. This prevents accidental commits directly to main.

Can I automatically trigger a code review workflow after opening a pull request?▼

Yes, you can configure an automated commit and push workflow that triggers a subsequent review-flow with a defined completion state right after opening the pull request. This streamlines handoff for code review.

Do I need any specific dependencies or tools installed to automate my commit and push workflow?▼

No specific dependencies or extra components are required to automate the commit, push, and pull request flow. The workflow operates independently to handle branch creation, PR formatting, and review triggering.

How do I share my pull request diff with my team after an automated PR is opened?▼

After the automated workflow opens your pull request, you can share the diff by running the command 'gh pr view --web' to view and share the changes directly in your web browser.