git_push

Name: git_push
Availability: InStock
Author: OpenAuthority

Push local branch commits to a remote Git repository.

8|Updated Mar 16, 2026

Search Tags:#automation #git #push #branch #error-handling #remote #version-control

Ready to run

npx skills add https://github.com/OpenAuthority/clawthority --skill git-push-openauthority

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git_push
Source: https://github.com/OpenAuthority/clawthority/tree/main/examples/skills/git_push
Command: npx skills add https://github.com/OpenAuthority/clawthority --skill git-push-openauthority

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes commits from the current branch to a remote git repository, enabling collaboration and remote sharing of work.

Core Features & Use Cases

Push the current branch to a named remote (default origin)
Return remote, branch, and status message on success
Handle errors: remote-not-found, auth-error, and rejected pushes, with clear guidance

Quick Start

Push the current branch to a remote repository by running the tool with optional remote and branch parameters.

Frequently Asked Questions about git_push

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

FAQPage Schema

How do I push local commits to a remote Git repository?▼

To push local commits to a remote Git repository, use this tool with optional remote and branch parameters. It publishes your local work from the current branch to the specified remote, defaulting to origin, and returns a success status with the remote and branch names.

Can I push commits to a specific remote branch other than origin?▼

Yes, you can push commits to a named remote branch other than origin. By providing the optional remote and branch parameters, the tool targets that specific remote repository and branch, returning the updated remote and branch details in the final status message.

Why does my Git push fail with a rejected error?▼

A Git push fails with a rejected error when remote changes conflict with your local commits. This tool specifically handles rejected pushes by returning a clear error message, alongside remote-not-found and auth-error handling, to guide you through resolving the branch conflict.

Do I need to specify both remote and branch parameters to publish local work?▼

No, you do not need to specify both parameters to publish local work. The tool pushes commits from the current local branch automatically, defaulting to the origin remote if parameters are omitted, and returns the pushed status, remote, branch, and a confirmation message.

What happens if authentication fails when pushing commits to a remote?▼

If authentication fails when pushing commits to a remote, the tool catches the auth-error and returns a clear message. This helps you quickly identify credential issues without crashing, ensuring you can fix permissions and retry the push to the remote repository.

How does automated Git push handle a remote-not-found error?▼

Automated Git push handles a remote-not-found error by catching the failure and returning a descriptive message. Instead of failing silently, the tool reports the missing remote repository issue so you can verify the remote name configuration and retry the push.