New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit Push PR

by dyoshikawa in dyoshikawa/rulesync

Commit current changes, push to remote, and create or update a pull request.

MITAuto-check passedDevelopment

Install Commit Push PR

skills CLI
$ npx skills add dyoshikawa/rulesync --skill commit-push-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync commit-push-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/commit-push-pr .claude/skills/commit-push-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit-push-pr
GitHub stars
1.5k
Token cost
~458 tokens
SKILL.md length
210 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Commit current changes, push to remote, and create or update a pull request.

  • Works in 5 steps: Check Current Branch → Stage and Commit Changes → Push to Remote → …
  • The user wants to commit and create a PR
  • SKILL.md covers Step 1: Check Current Branch, Step 2: Stage and Commit Changes, Step 3: Push to Remote and Step 4: Handle Pull Request, plus 1 more section
  • Calls git and gh

What it does

Commit Push PR is an agent skill from dyoshikawa/rulesync. Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.

Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Commit messages. It works with Git. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • The user wants to commit and create a PR
  • Push changes and open a pull request
  • Ship their current work as a PR

Example prompts

  • “/commit-push-pr”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Check Current Branch
  2. Stage and Commit Changes
  3. Push to Remote
  4. Handle Pull Request
  5. Report Result

What it can do on your machine

Read from SKILL.md and the folder at commit 85bcaf6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit Push PR loads about 458 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 210 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~458

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 85bcaf6, republished under its MIT licence (© dyoshikawa). 210 words, ~458 tokens.

Download SKILL.mdSave it as .claude/skills/commit-push-pr/SKILL.md (or your agent's skills folder).
name
commit-push-pr
description
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
targets
*

Commit, Push, and PR Management

Step 1: Check Current Branch

Run git branch --show-current to get the current branch name.

If the current branch is main or master:

  1. Generate a descriptive branch name based on the staged/unstaged changes
  2. Create and switch to the new branch: git checkout -b <new-branch-name>

Step 2: Stage and Commit Changes

  1. Run git status to check for changes
  2. If there are unstaged changes, stage them: git add .
  3. Analyze the changes and create a meaningful commit message
  4. Commit with: git commit -m "<commit-message>"

Step 3: Push to Remote

Push the branch to remote with upstream tracking:

bash
git push -u origin <branch-name>

Step 4: Handle Pull Request

Check if a PR already exists for this branch:

bash
gh pr view --json number,title,body 2>/dev/null
If PR does NOT exist:

Create a new PR:

bash
gh pr create --title "<title>" --body "<description>"

The PR description should include:

  • Summary of changes
  • Test plan (if applicable)
If PR already exists:
  1. Compare the current PR title and description with the actual changes
  2. If updates are needed (e.g., scope of changes has expanded), update the PR using GitHub API:
bash
gh api repos/<owner>/<repo>/pulls/<pr-number> -X PATCH -f title="<new-title>" -f body="<new-description>"

Note: Use gh api instead of gh pr edit to avoid GraphQL deprecation warnings. 3. If no updates are needed, skip this step

Step 5: Report Result

Output the PR URL and a summary of actions taken.

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/commit-push-pr of dyoshikawa/rulesync.

Open the folder on GitHubat commit 85bcaf6

Compare with similar skills

Commit Push PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Push PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Push PR this skilldyoshikawa/rulesync1.5k—~458Automated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Submit PR

    tisfeng/Easydict

    创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。

    15k GitHub stars~595 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo

  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • PRs Awaiting Author

    dyoshikawa/rulesync

    List open pull requests where the ball is in the author's court: CI is failing, review comments are unaddressed, or a maintainer question is awaiting the author's reply.

    1.5k GitHub stars~887 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Commit Push PR

What does Commit Push PR do?

Commit current changes, push to remote, and create or update a pull request. Commit Push PR is an agent skill from dyoshikawa/rulesync. Commit current changes, push to remote, and create or update a pull request.

When should I use Commit Push PR?

Commit Push PR fits situations like: the user wants to commit and create a PR; push changes and open a pull request; ship their current work as a PR.

How do I install Commit Push PR in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill commit-push-pr -a claude-code`. Or copy the skill folder (.rulesync/skills/commit-push-pr in dyoshikawa/rulesync) into .claude/skills/commit-push-pr in your project. Claude Code loads it when a task matches its description.

How do I install Commit Push PR in Codex?

Run `npx skills add dyoshikawa/rulesync --skill commit-push-pr -a codex`. Or copy the skill folder (.rulesync/skills/commit-push-pr in dyoshikawa/rulesync) into .agents/skills/commit-push-pr in your project. Codex loads it when a task matches its description.

Can I use Commit Push PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill commit-push-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-push-pr, .gemini/skills/commit-push-pr, .github/skills/commit-push-pr and .opencode/skills/commit-push-pr in your project.

What does Commit Push PR need to run?

Going by SKILL.md and its folder, Commit Push PR needs the command-line tools its instructions call (git and gh).

Does Commit Push PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit Push PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Commit Push PR use?

Commit Push PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Push PR use?

About 458 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Push PR?

Skills that share tags, products or a category with Commit Push PR: Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Push PR?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,507 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.