push

Stages all changes, commits with a generated message, and pushes to the remote repository.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill push-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/Wizarck/nexandro/tree/main/skills/push
Command: npx skills add https://github.com/Wizarck/nexandro --skill push-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the repetitive multi-step process of staging files, writing a commit message, and pushing to a remote by collapsing the entire Git workflow into a single command. ## Core Features & Use Cases - One-Step Git Workflow: Runs git status and diff analysis, stages all changes, commits, and pushes in a single invocation. - Automatic Commit Messages: Generates a concise conventional-style message (feat/fix/chore/docs prefix) from the diff when no message is provided, or uses your custom message. - Safe Defaults: Refuses to use --force or --no-verify, stops cleanly when there is nothing to commit, and reports errors without retrying dangerously. - Use Case: After finishing a feature branch edit, invoke the skill to instantly stage everything, commit with an auto-generated descriptive message, and push to origin without typing multiple git commands. ## Quick Start Ask the assistant to push all current changes, optionally providing a commit message such as "push with message fix login redirect bug".

Frequently Asked Questions about push

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

FAQPage Schema
How do I commit and push all changes in one step?▼

Invoke the push skill and it runs git status and git diff to review changes, stages everything with git add, creates a commit with a generated or custom message, and pushes to the remote. You receive a report with the commit hash and files changed count.

How are automatic commit messages generated from git diff?▼

The skill analyzes the output of git diff --stat and the change contents, then writes a concise message using a conventional prefix such as feat, fix, chore, or docs in one to two sentences. You can override this by passing your own message as an argument.

Can I provide my own commit message instead of an auto-generated one?▼

Yes, pass your message as the skill argument and it will be used verbatim as the commit message. A Co-Authored-By trailer for Claude is always appended automatically using HEREDOC formatting.

What happens if git push fails or the remote rejects it?▼

The skill reports the push error and stops without retrying. It never uses --force or --no-verify, so rejected pushes must be resolved manually, for example by pulling remote changes first.

What happens when there are no changes to commit?▼

The skill detects the clean working tree during the initial git status check, informs you there is nothing to commit, and stops without running git add, commit, or push.