Commit Push PR

Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.

75 stars 4 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sneg55/agent-starter

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sneg55/agent-starter --skill commit-push-pr
Manual install
git clone --depth 1 https://github.com/sneg55/agent-starter.git /tmp/agent-starter
mkdir -p ~/.claude/skills
cp -r /tmp/agent-starter/skills/commit-push-pr ~/.claude/skills/commit-push-pr

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Commit, Push, and Open PR

## Context

Gather this context first:
- `git status`
- `git diff HEAD`
- `git branch --show-current`
- `git diff main...HEAD` (or default branch)
- `gh pr view --json number 2>/dev/null || true`

## Git Safety Protocol

- NEVER update the git config
- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
- NEVER run force push to main/master, warn the user if they request it
- Do not commit files that likely contain secrets (.env, credentials.json, etc)
- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported

## Task

Analyze ALL changes that will be included in the pull request - look at ALL commits from `git diff main...HEAD`, not just the latest commit.

Based on the changes:

### 1. Create branch (if on main/master)
Use the format `username/feature-name`:
```
git checkout -b username/descriptive-feature-name
```

### 2. Create a single commit
Use heredoc syntax for the message:
```
git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"
```
- Follow the repo's commit message style (check `git log --oneline -10`)
- Focus on "why" not "what"
- Keep it concise (1-2 sentences)

### 3. Push the branch
```
git push -u origin HEAD
```

### 4. Create or update PR
Read the full skill on GitHub

Details

Skill name
commit-push-pr
Path
skills/commit-push-pr/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Commit Push PR skill do?

Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.

How do I install the Commit Push PR skill?

Claude Code plugin: /plugin marketplace add sneg55/agent-starter. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Commit Push PR popular?

It lives in sneg55/agent-starter, which has 75 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Adopt Project

75

sneg55/agent-starter

Apply agent-starter patterns to an EXISTING project - audits the codebase, proposes components by invasiveness tier (hooks, skills, CLAUDE.md, lint configs, patterns), and applies only what the developer approves. Use when the user says adopt, retrofit, "apply agent-starter to this project", or wants starter patterns in an existing codebase.

AI, LLMs & AgentsIn 1 list

Commit

75

sneg55/agent-starter

Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.

Git & Code ReviewIn 1 list

Dream

75

sneg55/agent-starter

Memory consolidation - review, merge, prune, and index memory files. Run periodically to keep memories organized and up-to-date.

Productivity & NotesIn 1 list

Clab

54

mberneti/clab

AI-powered review of self-hosted GitLab merge requests. Fetches MR diff, applies project-specific rules, posts inline comments. Can analyze past MRs to generate review rules.

Git & Code Review

Concurrent Branches

115

wdm0006/python-skills

Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool config, one aggregated test module, tracked build output), union-vs-recompute-vs-rebuild as three different correct resolutions, generated artifacts that must never be merged, non-deterministic serialization that makes every branch conflict, renumbered identifiers that git cannot show you, and why a clean auto-merge is not a passing test. Use when rebasing or merging a long-lived branch, resolving conf

Git & Code Review18

GitLab Stack Validator

93

rknall/claude-skills

Validates GitLab stack projects before deployment, ensuring proper architecture patterns, directory structure, secrets management, .env configuration, and Docker best practices. Use when users ask to validate a stack, check stack configuration, verify stack architecture, audit stack setup, or ensure stack deployment readiness.

Git & Code Review13

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.