Sets up Docusaurus i18n for Traditional Chinese, Simplified Chinese,
Japanese, and Korean: locale config, navbar/footer/sidebar UI chrome,
and translated content for intro, getting-started, understand, and
reference/commands. Untranslated pages fall back to English.
Pins explicit heading anchors ({#id}) on English source pages that are
linked to by fragment, so translated headings don't change the anchor
id and break cross-page links. Converts a handful of relative .md
links that crossed from an untranslated page into a now-translated
one, since Docusaurus resolves those per-locale and they'd otherwise
404 outside English.
3.6 KiB
sidebar_position
| sidebar_position |
|---|
| 2 |
pull
Pull from git remote and sync to all targets.
skillshare pull # Pull and sync
skillshare pull --dry-run # Preview
skillshare pull --force # Replace local with remote on first pull
When to Use
- Sync skills from another machine that pushed changes
- Get the latest skills after someone else pushed updates
- Start working on a new machine after
init --remote
What Happens
flowchart TD
CMD["skillshare pull"]
CHECK["1. Check repository status"]
PULL["2. Pull from remote"]
SYNC["3. Sync to all targets"]
CMD --> CHECK --> PULL --> SYNC
Options
| Flag | Description |
|---|---|
--dry-run, -n |
Preview without making changes |
--force, -f |
On first pull conflict, replace local skills with remote |
Git Root Scope
pull operates on the directory selected by the git_root config field (default: skills source). See commit — Git Root Scope for the scope table. If git_root was changed but the git repo still lives in another scope's directory, pull prints a "Git root mismatch" error with the exact git init / mv commands to fix it. See Changing the scope after init.
After pulling, pull syncs what the scope holds: skills runs sync, agents runs sync agents, root runs both, and extras runs sync extras.
Prerequisites
Your source directory must be a git repository with a remote:
# Check if ready:
skillshare status
# Shows: Git: initialized with remote
Local Changes Warning
If you have uncommitted changes, pull will fail:
$ skillshare pull
Local changes detected
Run: skillshare push
Or: cd ~/.config/skillshare/skills && git stash
Solutions:
# Option 1: Commit locally first, without pushing
skillshare commit -m "Local changes"
skillshare pull
# Option 2: Push your changes first
skillshare push
skillshare pull
# Option 3: Stash your changes
cd ~/.config/skillshare/skills
git stash
skillshare pull
git stash pop
First Pull with Existing Skills
On first pull (no upstream yet), if both local and remote already contain skill directories,
pull attempts a merge to combine both sides. If the merge succeeds, both local and remote skills are preserved.
If there are merge conflicts, pull fails with a non-zero exit code:
$ skillshare pull
Pull failed
Resolve manually: cd ~/.config/skillshare/skills && git merge --allow-unrelated-histories <remote branch>
Or force-pull: skillshare pull --force (replaces local with remote)
Resolve options:
# Resolve conflicts manually, then push
cd ~/.config/skillshare/skills
git add . && git commit
skillshare push
# Or discard local and take remote
skillshare pull --force
Examples
# Standard pull (most common)
skillshare pull
# Preview what would happen
skillshare pull --dry-run
# Replace local with remote on first-pull conflict
skillshare pull --force
Workflow
Typical workflow on a secondary machine:
# Start of day: get latest skills
skillshare pull
# ... work with AI tools ...
# End of day: share any new skills
skillshare collect claude # If you created new skills
skillshare push -m "Add new skill"
See Also
- commit — Commit locally without pushing
- push — Push to remote
- sync — Manual sync without pull
- Cross-Machine Sync — Full setup