git-sync-main

Original：🇨🇳 Chinese

Translated

Sync the local main branch with the latest code from the official upstream or origin remote

4installs

Sourcezc277584121/mygitplugin

Added on2026-04-27

NPX Install

npx skill4agent add zc277584121/mygitplugin git-sync-main

SKILL.md Content (Chinese)

View Translation Comparison →

Git Sync Main

Sync the latest main branch code to the local machine and switch to the main branch. Supports two scenarios: syncing forked projects from the official remote, and syncing your own projects from origin.

Trigger Conditions

Use this skill when the user requests to sync upstream code, update the main branch, or pull the latest main branch code.

Execution Steps

Check remote configuration:
```
git remote -v
```
to confirm if the
```
official
```
remote exists.
Execute in two scenarios based on whether the official remote exists:

Scenario 1: official remote exists (forked project)

Detect main branch name: Determine the main branch name (
```
main
```
or
```
master
```
) via
```
git remote show official
```
or by checking local branches.
Pull latest code from official:
```
git fetch official
```
.
Switch to local main branch:
```
git checkout <main-branch>
```
.
Sync code:
```
git reset --hard official/<main-branch>
```
to reset the local main branch to the latest state of official.
Push to origin:
```
git push origin <main-branch> --force-with-lease
```
to sync the main branch of your own forked remote.

Scenario 2: official remote does not exist (your own project)

Detect main branch name: Determine the main branch name (
```
main
```
or
```
master
```
) by checking local branches.
Pull latest code from origin:
```
git fetch origin
```
.
Switch to local main branch:
```
git checkout <main-branch>
```
.
Sync code:
```
git pull origin <main-branch>
```
to sync the local main branch to the latest state of origin.

Common Steps

Verify results:
```
git log --oneline -5
```
to display the latest few commits and confirm successful sync.

Notes

Always use
```
official
```
as the upstream remote name (instead of
```
upstream
```
) to maintain consistency.
For forked projects, use
```
--force-with-lease
```
instead of
```
--force
```
when pushing to origin for safer forced pushes.
If there are uncommitted changes currently, prompt the user to handle them first (stash or commit) to avoid losing work.