What is commit-push-pr?

A workflow for staging code changes, creating a commit, pushing it to a remote repository, and opening a pull request. A pull request is a proposed change for review before it is merged.

Use it when you want to commit relevant changes, send them to the shared repository, and request review on GitHub.

It brings the common handoff steps into one process while checking the repository state and confirming the proposed messages first.

commit-push-pr — Skill by vthinkdeveloper

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.

agentmods

npx agentmods add skills/vthinkdeveloper/vthink-agent-toolkit/commit-push-pr

Any agent

npx skills add vthinkdeveloper/vthink-agent-toolkit --skill commit-push-pr

Clone the repo

git clone --depth 1 https://github.com/vthinkdeveloper/vthink-agent-toolkit

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,395 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00059	$0.01395
Opus 5	$0.00030	$0.00698
Sonnet 5	$0.00012	$0.00279
Haiku 4.5	$0.00006	$0.00139

Measured yesterday against content hash 256008610c61, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

skills/commit-push-pr/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Commit, Push, and Open a PR

Overview

This skill handles the full commit → push → PR workflow. It confirms the commit message, PR title, and PR description with the user before doing anything irreversible.

Workflow

Step 1: Assess the Current State

Run these commands in parallel:

git status — see staged, unstaged, and untracked files (never use -uall)
git diff — see unstaged changes
git diff --cached — see already-staged changes
git log --oneline -5 — see recent commit style for message consistency
git branch --show-current — identify the current branch
git remote get-url origin — identify the remote

If there are no changes, inform the user and stop.

Check that gh is authenticated: run gh auth status. If not authenticated, tell the user to run gh auth login and stop.

Step 2: Stage Changes

Stage all modified and relevant files using git add with specific file paths.
Do NOT stage secrets or credentials (.env, credentials.json, *.key, *.pem). Warn the user and skip them.
Do NOT use git add -A or git add ..

Step 3: Generate a Commit Message

Analyze git diff --cached and draft a commit message following Conventional Commits (https://www.conventionalcommits.org/en/v1.0.0/).

Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

Type	When to use
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only
`style`	Formatting, whitespace — no logic change
`refactor`	Code restructuring, no feature or fix
`perf`	Performance improvement
`test`	Adding or updating tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Maintenance, no src/test changes

Rules

Description: lowercase, imperative mood, no period, under 72 characters
Body: explain why, not what — separated by a blank line
For breaking changes: add ! after type/scope and a BREAKING CHANGE: footer

Always append as the final footer:

Co-Authored-By: Claude <[email protected]>

Read the full file on GitHub · 215 lines

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.

yesterday First seen · 215 lines · 59 tokens per session scan A 256008610c61

Subscribe to this mod's changes

commit-push-pr is a skill published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,395 once invoked, about $0.0003 per session on Opus 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-31.

Code review Git and workflow Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens