home / skills / hikaruegashira / agent-skills / commit-push-pr-flow

commit-push-pr-flow skill

This skill automates commit push and PR flow after task completion, creating a branch, opening a PR, and sharing diffs.

npx playbooks add skill hikaruegashira/agent-skills --skill commit-push-pr-flow

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

464 B

---
name: commit-push-pr-flow
description: |
    タスク完了後に自律的に実行する必要があるフロースキルです。
    Trigger: task completed, ready to submit code
model: haiku
---

Commit, push, and open a pr

- create branch(if current branch in default) and pr
- following pr template
- description in japanese
- 提出後は gh pr view --web で差分を共有して完了してください
- 完了後 review-flow を呼び出します

Overview

This skill automates the final commit-push-PR workflow after a task is completed and code is ready to submit. It creates a branch when needed, populates the pull request using the repository template and a Japanese description, and triggers the next review flow once submission is done.

How this skill works

When a task reports completion, the skill checks the current branch and creates a new branch if you are on the default branch. It stages and commits changes, pushes the branch to the remote, and opens a pull request using the repository's PR template with a Japanese description. After creating the PR it opens the diff in the browser (gh pr view --web) and invokes the review-flow skill to continue the process.

When to use it

A development task has completed and code is ready to be submitted.
You are on the default branch and need an automatic feature branch created.
You want PR content formatted with the repository PR template and a Japanese description.
You need the diff shared in the browser immediately after submission.
You want an automated handoff to the review-flow for code review.

Best practices

Ensure working tree is clean or stash uncommitted changes before triggering the flow.
Write clear, concise Japanese descriptions that summarize changes and intent.
Confirm repository PR template exists to populate PR fields correctly.
Use descriptive branch names including task ID or short summary.
Review the generated commit message and PR body before final push if manual edits are needed.

Example use cases

After finishing a bug fix, automatically create branch, commit, push, and open a PR using the template.
For a completed feature task, generate a feature branch and submit a PR with a Japanese summary for reviewers.
When on main or master, avoid accidental commits by automatically switching to a new branch before pushing.
Share the diff with stakeholders immediately by opening the PR in the web browser.
Hand off newly submitted code to the review-flow for automated or human review steps.

FAQ

What happens if I'm already on a feature branch?

The skill will use the current branch and proceed to commit, push, and open a PR without creating a new branch.

Is the PR description always written in Japanese?

Yes — this flow fills the PR description in Japanese per repository guidance, but you can edit it before finalizing the PR.

How is the diff shared after PR creation?

The skill runs gh pr view --web to open the PR diff in the default browser for immediate sharing.