git-add-commit-push

Stages all changes, generates a commit message from the diff, commits, and pushes to the current branch.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mcmurrym/coding-agent-skills --skill git-add-commit-push-mcmurrym
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-add-commit-push
Source: https://github.com/mcmurrym/coding-agent-skills/tree/main/agent-skills/git-add-commit-push
Command: npx skills add https://github.com/mcmurrym/coding-agent-skills --skill git-add-commit-push-mcmurrym

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually running git add, git commit, and git push for every change is repetitive, and writing commit messages from scratch slows down the flow. This Skill automates the entire sequence in one zero-input run, including auto-generating a commit message from the actual diff. ## Core Features & Use Cases - Zero-Input Git Flow: Stages all changes with git add -A, commits with an auto-generated message, and pushes to origin on the current branch in one script run. - Secret Protection: Refuses to commit real .env files while allowing template files like .env.example, .env.sample, and .env.template. - Flexible Options: Supports --dry-run previews, --no-push, custom remote (-r), branch (-b), and message (-m) overrides. - Use Case: After finishing a feature edit, ask the agent to commit and push everything; it inspects the diff, drafts a message like "chore: update src", commits, pushes, and reports the new commit hash. ## Quick Start Ask the agent to stage all current changes, generate a commit message from the diff, commit, and push to the current branch.

Frequently Asked Questions about git-add-commit-push

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

FAQPage Schema
How do I stage, commit, and push all git changes in one command?▼

Run the bundled git-add-commit-push.sh script with no arguments. It executes git add -A, generates a commit message from the diff, commits, and pushes to origin on the current branch automatically.

How to auto-generate a git commit message from the diff?▼

The script inspects git diff --name-status to count changed files and derive a summary path, producing a message like "chore: update <path>". You can override it anytime with the -m flag.

Can I commit without pushing to the remote?▼

Yes, pass the --no-push flag to skip the push step. The script still stages all changes and commits locally, and you can push manually later with git push origin HEAD.

Does the script prevent committing .env secret files?▼

Yes, after staging it scans staged files and refuses to commit if any .env or .env.* file is detected. Template files such as .env.example, .env.sample, and .env.template are explicitly allowed.

Why does the git commit script fail with no changes?▼

The script checks git status --porcelain first and exits with an error if the working tree is clean. It also fails on a detached HEAD because the current branch cannot be determined for pushing.

When should I not use this full-staging git workflow?▼

Avoid it when you need partial staging of specific files or hunks, since it always runs git add -A. For selective commits, stage files manually and commit with git commit directly.