commit-push

Commit local repository changes and push them to a remote.

9|Updated Dec 21, 2025

Search Tags:#git #workflow #commit #push #branch #remote #version-control

Ready to run

npx skills add https://github.com/gewoonseba/dotfiles --skill commit-push-gewoonseba

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/commit-push
Command: npx skills add https://github.com/gewoonseba/dotfiles --skill commit-push-gewoonseba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of committing changes with a meaningful message and pushing them to the remote repository, reducing manual steps and mistakes.

Core Features & Use Cases

Commit all changes (staged and unstaged) with a descriptive message that explains the reason for the change.
Push to the remote repository with correct branch tracking and verification of success.
Use Case: When finishing work on a feature, run this Skill to ensure changes are committed with context and pushed to origin for collaboration.

Quick Start

Commit all changes with a descriptive message and push to the remote.

Frequently Asked Questions about commit-push

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

FAQPage Schema

How do I commit all changes with a descriptive message and push to a remote branch?▼

You can commit all changes with a descriptive message and push to a remote branch by automating the staging, committing, and pushing process while verifying branch tracking and success. This ensures changes are committed with context and pushed to origin for collaboration.

How does committing and pushing work for daily development workflows on feature branches?▼

Committing and pushing for daily development workflows works by staging local changes, applying a descriptive commit message explaining the reason for the change, and pushing to the correct remote branch with verification of success. This reduces manual steps and mistakes in collaborative projects.

Do I need to manually stage files before committing and pushing to a remote repository?▼

You do not need to manually stage files before committing and pushing to a remote repository. The process commits all changes, including both staged and unstaged files, before applying a descriptive message and pushing to the correct remote branch.

What's the best way to ensure correct branch tracking when pushing commits to origin?▼

The best way to ensure correct branch tracking when pushing commits to origin is to automate the push process with built-in verification of success. This handles proper remote branch tracking automatically, preventing manual mistakes during collaborative version control workflows.

Why does pushing to a remote repository fail after committing changes locally?▼

Pushing to a remote repository fails when branch tracking is incorrect or verification of success detects an issue with the remote connection. Automating the commit and push process ensures proper staging, correct remote tracking, and verified success to prevent these failures.