commit-push-sync

Automate git commit, pull with rebase, and push workflows.

11|2|Updated May 29, 2025
One-click install
npx skills add https://github.com/yulonglin/dotfiles --skill commit-push-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-sync
Source: https://github.com/yulonglin/dotfiles/tree/main/claude/skills/commit-push-sync
Command: npx skills add https://github.com/yulonglin/dotfiles --skill commit-push-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the complete git workflow to commit local changes, pull with rebase to maintain a linear history, and push updates to the remote, reducing manual steps and human error.

Core Features & Use Cases

  • End-to-end git workflow automation: commit changes following best practices, pull with --rebase to preserve linear history, and push to the remote.
  • Handles uncommitted work via an explicit commit path or an optional stash-based sync, with clear prompts if conflicts arise.
  • Guides conflict resolution with step-by-step instructions and safety checks to prevent destructive actions and preserve history.

Quick Start

Initiate a full commit-push-sync workflow for the current repository state, including staging uncommitted changes, performing a pull --rebase, resolving conflicts with guided prompts, and pushing to the remote.

Frequently Asked Questions about commit-push-sync

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

FAQPage Schema
How do I automate git commit, pull --rebase, and push in one workflow?

Automating git commit, pull --rebase, and push stages local changes, syncs with remote to preserve linear history, and safely pushes updates. It handles uncommitted work via explicit commits or stash-based sync.

How does pull --rebase handle uncommitted changes during a sync?

Pull --rebase handles uncommitted changes by using an optional stash-based sync. It stashes your work, applies remote updates, and restores changes, prompting you if conflicts arise.

Can I use this to resolve git conflicts during an automated push?

You can use this to resolve git conflicts during an automated push. It provides step-by-step guidance for conflict resolution and includes safety checks to prevent destructive actions.

What is the best way to maintain linear history when collaborating on git branches?

Maintaining linear history when collaborating on git branches requires pulling with --rebase before pushing. This replays your local commits on top of remote changes, avoiding merge commits.

Does this automated git workflow work with bug fixes and feature branches?

This automated git workflow works with bug fixes and feature branches. It applies the end-to-end commit, rebase, and push cycle to any collaborative development scenario.

Why does my automated git push fail when local changes conflict with remote updates?

An automated git push fails when local changes conflict with remote updates because the histories have diverged. The workflow detects this, halts the push, and guides you through resolving rebase conflicts.