push

Stage all changes, commit with an auto-generated message, and push to the remote.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the Git workflow by staging all local changes, creating a descriptive commit, and pushing to the remote in a single step.

Core Features & Use Cases

  • Stage all changes with git add .
  • Create a descriptive commit message either from the provided ARGUMENTS or auto-generated from the diff.
  • Push to the configured remote and report the commit hash, message, and changed files.
  • Use in solo projects, small teams, or scripted workflows to enforce consistency.

Quick Start

Run the workflow to stage all changes, commit with an auto-generated message, and push to the remote in one step.

Frequently Asked Questions about push

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

FAQPage Schema
How do I stage, commit, and push all local changes in one step?

You can automate the git workflow to stage, commit, and push in one step by adding all changes, generating a commit message from the diff, and pushing to the remote repository.

How does auto-generated commit message creation work from a git diff?

Auto-generated commit messages are created by reading the current git diff to produce a concise message if none is provided, then applying it to the staged changes.

Can I use automated git push workflows for small team version control?

Yes, automated git push workflows suit solo projects and small teams to enforce consistency. They ensure changes are consistently recorded across any Git repository with a standardized commit message.

What is the best way to enforce consistent git commit messages across a project?

The best way to enforce consistent git commit messages is to automate the workflow with auto-generated messages from the diff and a Co-Authored-By footer, ensuring uniform formatting.

When should I not use a single-step git commit and push automation?

You should avoid single-step git commit and push automation when you need selective staging, as it stages all changes with git add . and immediately pushes to the remote.