Synchronize a local git branch with origin/main via fetch, merge, commit, and push.
npx skills add https://github.com/YoniChechik/claude-code-config --skill sync-yonichechik
Please help me install this Agent Skill. Skill: sync Source: https://github.com/YoniChechik/claude-code-config/tree/main/skills/sync Command: npx skills add https://github.com/YoniChechik/claude-code-config --skill sync-yonichechik
This Skill automates keeping a local git branch synchronized with origin/main by merging, committing, and pushing to remote, preventing divergence and stale work.
Execute a synchronization cycle with these commands: git fetch origin git merge origin/main
git add -A git commit -m "<your generated message>" git push
High-intent search queries and answers about installing and using this skill.
To keep your local git branch synchronized with origin main, you need to fetch remote updates, merge origin/main into your branch, resolve any conflicts, commit the changes, and push to remote. This prevents branch divergence and stale work.
Resolving git conflicts during an origin main merge requires fetching and merging remote changes, manually resolving simple conflicts that arise, staging all files with git add, and generating a commit to push the synchronized state back to remote.
Automating git fetch, merge, and push for collaborative development involves running a deterministic workflow that fetches origin, merges origin/main, resolves simple conflicts, generates clear commit messages, and pushes updates so teams stay aligned.
Your feature branch diverges from origin main when local and remote histories split. Fix divergence by fetching origin, merging origin/main into your local branch, resolving conflicts, committing, and pushing to ensure local HEAD is ahead of or equal to origin.
Yes, you can use this sync workflow to prepare a feature branch before a pull request. It fetches and merges origin/main, resolves simple conflicts, and pushes updates to ensure your branch is current and non-divergent before submitting.
Branch synchronization works when your local HEAD is behind origin main by fetching the latest remote state, merging origin/main into your current branch, and pushing the updated commit history to ensure local and remote repositories match.
gonzalezpazmonicaSynchronize SaviaHub repositories between local and remote instances with Git.
flurdyRebase the current feature branch onto origin/main with conflict handling and status reporting.
willyu1007Enforce Git commit message formats, branch naming, and pull request best practices.
JacobPEvansRebase pull requests onto main with signed commits and GitHub API checks.
