git-push

Push the current Git branch to the remote with safety checks.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/biwakonbu/cc-plugins --skill git-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-push
Source: https://github.com/biwakonbu/cc-plugins/tree/main/plugins/git-actions/skills/push
Command: npx skills add https://github.com/biwakonbu/cc-plugins --skill git-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and safeguards the Git push workflow, ensuring the current branch's commits reach the remote repository reliably.

Core Features & Use Cases

  • Push the current branch to the origin with safety checks.
  • Validate upstream configuration and detect uncommitted changes before pushing.
  • Use case: when finishing a feature, push commits without risking divergence or overwriting remote changes.

Quick Start

Push the current branch to the remote repository, ensuring upstream is configured and no uncommitted changes exist.

Frequently Asked Questions about git-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely push commits to a remote Git branch?

Push commits safely by validating upstream configuration and detecting uncommitted changes before executing the push, ensuring the current branch syncs with the remote repository without risking divergence or overwriting remote changes.

What is the best way to push a new Git branch to origin?

Push a new Git branch to origin by validating upstream configuration and using the --set-upstream option with explicit confirmation, establishing the remote tracking relationship securely for the current branch.

Can I force push a Git branch without overwriting remote changes?

Force push a Git branch without overwriting unexpected remote changes by using the --force-with-lease option, which validates the remote state and requires explicit user confirmation before proceeding with the push.

Why does my Git push fail when uncommitted changes exist?

Git push workflows fail or risk state corruption when uncommitted changes exist, so this process detects local modifications and enforces a clean working directory before pushing the current branch to the remote.

Does this Git push workflow support the git -C command for remote repositories?

This Git push workflow does not support the git -C command; it enforces practical requirements by running all version control commands within the current working directory to maintain safe push validation.