push-all

Name: push-all
Availability: InStock
Author: dunaevdmitriys-dev

Commit and push all local Git changes to the tracked remote repository.

Updated Aug 23, 2026

Search Tags:#git #commit #push #repository sync #co-authored-by #cli workflow #change reporting

Ready to run

npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill push-all-dunaevdmitriys-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: push-all
Source: https://github.com/dunaevdmitriys-dev/directum-mcp-server/tree/main/skills/push-all
Command: npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill push-all-dunaevdmitriys-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction and risk of forgetting files by giving you a single command to stage, commit, and push every current change—so your work is always safely reflected in the remote repository.

Core Features & Use Cases

Bulk stage & commit: Adds all changes (staged, unstaged, and untracked) in one consistent commit.
Commit-message guidance: Encourages a concise message and consistent project style, including a required Co-Authored-By line.
Push reporting: Produces a clear post-push summary with branch, commit hash, and file count.
When to use: Ideal at the end of a work session or whenever your “git add -A && commit && push” workflow should be performed reliably.

Quick Start

Use the push-all skill to commit and push all current repository changes with a single action.

Frequently Asked Questions about push-all

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

FAQPage Schema

How do I commit and push all local Git changes at once?▼

Push-all automates committing and pushing all local Git changes to the tracked remote repository in one workflow. It runs git diff and git status for message context, performs git add -A, creates a commit with required Co-Authored-By attribution, and pushes while reporting branch, commit hash, and changed file count.

What is the best way to synchronize untracked files to a remote repository?▼

Synchronizing untracked files requires a workflow that stages all changes indiscriminately using git add -A before committing. This guarantees that every untracked, modified, or unstaged file is included in a single bulk commit before the push action.

How does automated git push reporting work for end-of-session commits?▼

Automated git push reporting works by generating a post-push summary that outputs the exact branch name, the new commit hash, and the total changed file count. This provides clear verification after executing a bulk commit and push synchronization workflow.

When do I need to use a bulk commit and push workflow for Git?▼

You need to use a bulk commit and push workflow for Git during end-of-session synchronization or when publishing bulk changes. It prevents the risk of forgetting files by consistently staging all tracked, unstaged, and untracked file scenarios before pushing.

Does bulk Git staging with git add -A require a Co-Authored-By line?▼

Bulk Git staging using git add -A requires a Co-Authored-By attribution line in the commit message to maintain consistent project style. The workflow enforces this required metadata while generating a concise commit message based on git diff context.

Why does my bulk Git push workflow miss untracked repository files?▼

A bulk Git push workflow misses untracked repository files if it only stages currently tracked changes instead of using git add -A. Automating the staging of staged, unstaged, and untracked file scenarios ensures all local changes are safely reflected in the remote repository.