Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mhattingpete avatar

Git Pushing

  • 378 installs
  • 656 repo stars
  • Updated July 25, 2026
  • mhattingpete/claude-skills-marketplace

git-pushing is a Claude agent skill that pushes reviewed branches to remotes, sets upstream tracking, and completes handoff from local commits to CI or pull-request review for developers avoiding manual git push mistakes

About

git-pushing is a mhattingpete/claude-skills-marketplace agent skill that safely pushes reviewed local branches to remotes and configures upstream tracking so CI pipelines and pull-request review start without manual git errors. It handles the fragile transition between finished local commits and remote visibility—correct remote names, first-push upstream flags, and branch tracking setup that developers often mistype under deadline pressure. Developers invoke git-pushing after code review passes locally and before opening or updating a pull request that depends on remote branch presence. The skill reduces failed pushes, wrong-remote mistakes, and untracked branches that leave CI idle. Reach for git-pushing when handoff from local worktrees to team review workflows must be reliable and repeatable across contributors who may not memorize git push variants. Outputs are pushed remote branches with upstream configured, ready for GitHub Actions, GitLab CI, or PR creation steps.

  • Upstream branch setup
  • Safe push workflows
  • Remote sync checks
  • PR-ready branch hygiene
  • Recover from push errors

Git Pushing by the numbers

  • 378 all-time installs (skills.sh)
  • +7 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #123 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill git-pushing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs378
repo stars656
Last updatedJuly 25, 2026
Repositorymhattingpete/claude-skills-marketplace

How do you push a branch and set upstream tracking?

Push reviewed branches to remotes, set upstream tracking, and complete the handoff from local commits to CI or pull-request review without manual git mistakes.

Who is it for?

Developers finishing local commits who need reliable git push and upstream setup before CI or pull-request review starts.

Skip if: Developers still writing unreviewed local changes who have not finished commits or branch preparation before remote push.

When should I use this skill?

A developer asks to push a reviewed branch, set upstream tracking, or complete handoff from local commits to CI or pull-request review.

What you get

Remote branch with upstream tracking configured, pushed commits visible to CI, and pull-request pipeline ready for review handoff.

  • Pushed remote branch
  • Upstream tracking configuration

Files

SKILL.mdMarkdownGitHub ↗

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

  • Explicitly asks to push changes ("push this", "commit and push")
  • Mentions saving work to remote ("save to github", "push to remote")
  • Completes a feature and wants to share it
  • Says phrases like "let's push this up" or "commit these changes"

Workflow

ALWAYS use the script - do NOT use manual git commands:

bash skills/git-pushing/scripts/smart_commit.sh

With custom message:

bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"

Script handles: staging, conventional commit message, Claude footer, push with -u flag.

Related skills

How it compares

Use git-pushing for post-review remote handoff; use commit-message skills when the task is formatting local commits before push.

FAQ

What does git-pushing handle after local review?

git-pushing pushes reviewed branches to remotes, sets upstream tracking, and completes handoff to CI or pull-request review. The mhattingpete/claude-skills-marketplace skill targets the transition from finished local commits to remote visibility without common push mistakes.

When should developers invoke git-pushing?

Developers should invoke git-pushing after local commits are reviewed and ready for remote visibility, before opening or updating pull requests. The skill configures upstream tracking so CI pipelines and team review workflows start reliably.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.