code-sync

Original：🇺🇸 English

Translated

1 scripts

Use when syncing all git repos under ~/code across machines, typically at end-of-day (push) or start-of-day (pull). Triggers on「同步代码」「code-sync」「下班同步」「上班更新」.

2installs

Sourceniracler/skill

Added on2026-02-09

NPX Install

npx skill4agent add niracler/skill code-sync

SKILL.md Content

View Translation Comparison →

Code Sync

Batch sync all git repos under

~/code

— push (end-of-day) or pull (start-of-day).

Prerequisites

Tool	Type	Required	Install
git	cli	Yes	`brew install git` or git-scm.com
git-workflow	skill	No	Included in `npx skills add niracler/skill` (used for dirty repo commits)

Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.

Mode Selection

User says	Mode
「下班同步」or "push"	Push
「上班更新」or "pull"	Pull
「同步代码」「code-sync」	Ask user

Workflow (shared by both modes)

Scan → 2. Categorize → 3. Batch action (auto, no confirmation) → 4. Handle exceptions (interactive) → 5. Summary

If all repos are up-to-date, report that and stop.

Scan

bash

bash scripts/scan.sh           # Push: local data only
bash scripts/scan.sh --fetch   # Pull: fetch remote first (10s timeout/repo)

Output: JSON array with fields

path

,

name

,

branch

,

remote

,

remote_url

,

dirty_count

,

has_upstream

,

ahead

,

behind

, and

fetch_error

(only on

--fetch

failure).

Categorize

Push mode:

Category	Condition	Action
up-to-date	`dirty_count == 0 && ahead == 0`	Report
needs-push	`dirty_count == 0 && ahead > 0`	Auto `git push`
dirty	`dirty_count > 0`	Interactive
no-upstream	`has_upstream == false`	Ask user

Pull mode:

Category	Condition	Action
up-to-date	`dirty_count == 0 && behind == 0`	Report
needs-pull	`dirty_count == 0 && behind > 0`	Auto `git pull --ff-only`
dirty+behind	`dirty_count > 0 && behind > 0`	Interactive
fetch-error	`fetch_error == true`	Report, skip

Exception Handling

Situation	Steps
Dirty repo (push)	`git diff --stat` + `git status` → describe to user → ask: commit, stash, or skip. If commit, use git-workflow skill to commit and push.
No upstream (push)	Report → ask: set upstream and push ( `git push -u origin <branch>` ), or skip
ff-only fails (pull)	`git log --oneline HEAD..@{u}` + `@{u}..HEAD` → explain divergence → suggest: rebase, merge, or skip
Dirty + behind (pull)	Report both issues → ask: stash and pull (stash, pull --ff-only, pop), or skip

Summary

Group repos by outcome after all operations complete:

text

## {Push|Pull} Summary

{Pushed|Updated} (N):
  - repo-name (branch, N commits)
Already up-to-date (N):
  - repo-a, repo-b, ...
Resolved (N):
  - repo-c: action taken
Skipped (N):
  - repo-d: reason

Common Issues

Issue	Fix
`scan.sh` finds 0 repos	Check `~/code/*/` has git repos
`fetch_error`	Check network, SSH keys
ff-only fails	Rebase or merge manually
Push rejected	Pull first, then push