commit-push-pr

commit-push-pr is a skill for Claude Code, Codex from dyoshikawa/rulesync. It costs 50 tokens per session (471 once invoked), scanned A, original, MIT.

A Git workflow for committing current code changes, pushing them to a remote repository, and creating or updating a pull request. A remote repository is the shared online copy of a project.

In plain words
What is it for?
Use it to check the branch, group and commit changes, push a new branch, and open or update its pull request. It also handles work started on the main branch by creating a feature branch.
Why use it?
It coordinates the steps needed to turn local work into a reviewable contribution and keeps the pull-request description aligned with the changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check the branch, group and commit changes, push a new branch, and open or update its pull request. It also handles work started on the main branch by creating a feature branch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dyoshikawa/rulesync/commit-push-pr
About the project

Rulesync is a command-line tool that generates configuration for different AI development tools from a shared set of rules. Developers use it to keep instructions, commands, MCP settings, ignore files, subagents, and skills consistent across coding agents. Catalogue skills support workflows built around Rulesync.

dyoshikawa/rulesync · 1,520 stars · on GitHub · rulesync.dyoshikawa.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add dyoshikawa/rulesync --skill commit-push-pr
Clone the repo
git clone --depth 1 https://github.com/dyoshikawa/rulesync

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for commit-push-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/dyoshikawa/rulesync/commit-push-pr/github.svg)](https://agentmods.dev/skills/dyoshikawa/rulesync/commit-push-pr)
Your own site
<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/commit-push-pr"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/commit-push-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for commit-push-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/commit-push-pr"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00471
Opus 5.5 $0.00020 $0.00188
Sonnet 5.5 $0.00010 $0.00094
Haiku 4.5 $0.00005 $0.00047

Measured 1mo ago against content hash 4fc162ad16b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-push-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.rulesync/skills/commit-push-pr/SKILL.md · 72 lines

What it actually says

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:

git push -u origin <branch-name>

Step 4: Handle Pull Request

Check if a PR already exists for this branch:

gh pr view --json number,title,body 2>/dev/null

If PR does NOT exist:

Create a new PR:

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:
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.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 72 lines · 50 tokens per session scan A 4fc162ad16b0

Subscribe to this mod's changes

commit-push-pr is a skill published in the GitHub repository dyoshikawa/rulesync (1,520 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 471 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

chinese-commit

A guide for writing Git commit messages in a shared format: an English change type followed by a short Chinese summary. Git commits are saved descriptions of changes to a codebase.

Wade-DevCode/awesome-coding-skills-cn · 28 tokens

caveman-commit

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

JuliusBrussee/caveman · 38 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

chinese-commit-conventions

A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.

jnMetaCode/superpowers-zh · 65 tokens

run-work

Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.

hashgraph-online/awesome-codex-plugins · 68 tokens

app_tagline_backfill

Give apps built on this instance a share-card tagline when their app.yaml has none. Runs automatically once after Rome upgrades (AUTO mode, list supplied by the caller) or on request from the guardian ("add taglines to my apps", MANUAL mode, confirm before writing). Only touches editable mode: "source" apps — never…

rome-os/rome · 0 tokens