How do I install the Commit Push Pr skill?

Run npx skillmds@latest add tomevault-io/commit-push-pr-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit Push Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Push Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Push Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Push Pr?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Push Pr by tomevault-io — Agent Skill

Name: Commit Push Pr
Author: tomevault-io

Commit Push Pr

Automate the workflow from creating a branch to opening a GitHub pull request. Use when the user says "create a PR", "commit and push", "push changes and create PR", or "open a pull request". Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

commit-push-pr

Automate creating branches, commits, and pull requests.

Trigger Examples

"Create a PR"
"Commit and push"
"Push changes and create PR"
"Open a pull request"

Prerequisites

GitHub CLI (gh) is installed and authenticated
Changes exist in the working tree
Local quality checks have been run manually

Execution Flow

1. Generate Branch Name

Derive branch prefix from commit type:

Type	Branch Format
feat(scope): ...	`feature/scope-<summary>`
fix(scope): ...	`fix/scope-<summary>`
refactor(scope): ...	`refactor/scope-<summary>`
docs	`docs/<summary>`
No scope	`<type>/<summary>`

Use lowercase kebab-case
Translate Japanese summaries to English

2. Create or Reuse Branch

git rev-parse --abbrev-ref HEAD

If on base branch: create new branch with git checkout -b <branch>
If on feature branch: confirm reuse with user

3. Stage and Commit Changes

git status --porcelain
git add -A
git commit -m "<message>"

If no staged changes, inform user and stop.

4. Push to Remote

git push -u origin <branch>

Prompt: "Ready to create a PR now?"

5. Generate PR Body

Gather context:

git log origin/<base>..HEAD --oneline
git diff origin/<base>...HEAD --stat

Populate PR sections:

Purpose / Background - Why the change exists
Summary of changes - Major modifications by layer
Verification steps - Commands and manual checks
Impact / Compatibility - API/schema changes, breaking behavior
Linked issues / docs - Reference tickets or docs
Checklist - Mark satisfied items

6. Create the PR

gh pr create \
  --base <base> \
  --title "$(git log -1 --pretty=%s)" \
  --body-file /tmp/pr-body.md \
  --assignee "nozomi-koborinai"

Ask if draft PR is preferred.

7. Output PR URL

Display the link for user review.

AI Analysis Points

Classify the change set:

Frontend: app/ or app/src
Infrastructure: infra/**
Documentation: docs/, AGENTS.md, README.md
Tests: *.test.ts, tests/

Detect high-risk changes:

Database schema changes
API contract changes
Infrastructure modifications
Security-sensitive updates

Notes

Assume origin points to GitHub
PR descriptions should be high quality from the start
If branch exists, ask user for alternative name

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: commit-push-pr-5description: Automate the workflow from creating a branch to opening a GitHub pull request. Use when the user says "create a PR", "commit and push", "push changes and create PR", or "open a pull request". Use when this capability is needed.---# commit-push-prAutomate creating branches, commits, and pull requests.## Trigger Examples- "Create a PR"- "Commit and push"- "Push changes and create PR"- "Open a pull request"## Prerequisites- GitHub CLI (`gh`) is installed and authenticated- Changes exist in the working tree- Local quality checks have been run manually## Execution Flow### 1. Generate Branch NameDerive branch prefix from commit type:| Type | Branch Format ||------|---------------|| feat(scope): ... | `feature/scope-<summary>` || fix(scope): ... | `fix/scope-<summary>` || refactor(scope): ... | `refactor/scope-<summary>` || docs | `docs/<summary>` || No scope | `<type>/<summary>` |- Use lowercase kebab-case- Translate Japanese summaries to English### 2. Create or Reuse Branch```bashgit rev-parse --abbrev-ref HEAD```- If on base branch: create new branch with `git checkout -b <branch>`- If on feature branch: confirm reuse with user### 3. Stage and Commit Changes```bashgit status --porcelaingit add -Agit commit -m "<message>"```If no staged changes, inform user and stop.### 4. Push to Remote```bashgit push -u origin <branch>```Prompt: "Ready to create a PR now?"### 5. Generate PR BodyGather context:```bashgit log origin/<base>..HEAD --onelinegit diff origin/<base>...HEAD --stat```Populate PR sections:1. **Purpose / Background** - Why the change exists2. **Summary of changes** - Major modifications by layer3. **Verification steps** - Commands and manual checks4. **Impact / Compatibility** - API/schema changes, breaking behavior5. **Linked issues / docs** - Reference tickets or docs6. **Checklist** - Mark satisfied items### 6. Create the PR```bashgh pr create \ --base <base> \ --title "$(git log -1 --pretty=%s)" \ --body-file /tmp/pr-body.md \ --assignee "nozomi-koborinai"```Ask if draft PR is preferred.### 7. Output PR URLDisplay the link for user review.## AI Analysis Points**Classify the change set:**- Frontend: `app/` or `app/src`- Infrastructure: `infra/**`- Documentation: `docs/`, `AGENTS.md`, `README.md`- Tests: `*.test.ts`, `tests/`**Detect high-risk changes:**- Database schema changes- API contract changes- Infrastructure modifications- Security-sensitive updates## Notes- Assume `origin` points to GitHub- PR descriptions should be high quality from the start- If branch exists, ask user for alternative name---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nozomi-koborinai) — claim your Tome and manage your conversions.

Frequently asked questions