Sync github forks

Skill nainishshafi/developer-productivity-skills/.github/skills/sync-github-forks

Reusable AI skills for Claude Code and GitHub Copilot — scan READMEs, sync forks, create skills, lint Python, and scan for security vulnerabilities

Install

npx -y skills add nainishshafi/developer-productivity-skills --skill sync-github-forks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This skill should be used when the user asks to "sync github forks", "sync forks", "pull all my forks", or wants to create a bash script that clones or pulls all their GitHub forked repositories.

SKILL.md

2.2 KB, as published. Nobody here has run it

IMPORTANT: Both scripts are already bundled with this skill. Do NOT create new files. Detect the OS and run the appropriate existing script:

Windows → scripts/sync-forks.ps1

Linux / macOS → scripts/sync-forks.sh

The bundled scripts sync all GitHub forks by cloning missing repos and pulling existing ones. They use the gh CLI for API calls — no token needed.

Prerequisites

gh CLI installed and authenticated (gh auth login)
git on PATH
Linux/macOS only: jq on PATH
SSH key added to GitHub (for clone/pull via SSH)

Usage

Both scripts already exist — detect the OS and run the correct one. Do not create any new files.

Windows (PowerShell):

# Optional: override clone location (default: ~\git-repos)
$env:BASE_DIR = "$env:USERPROFILE\code"

pwsh scripts/sync-forks.ps1

Linux / macOS (bash):

# Optional: override clone location (default: ~/git-repos)
export BASE_DIR=~/code

bash scripts/sync-forks.sh

What the Script Does

Checks that gh, jq, and git are on PATH.
Derives your GitHub username automatically via gh api user.
Paginates GET /user/repos?type=forks&per_page=100&page=N via gh api until all forks are fetched.
For each fork:
- Local dir exists → git pull origin <current-branch> (fast-forward).
- Local dir missing → git clone <ssh_url> $BASE_DIR/<name>.
Prints a final summary: Done — cloned N, pulled N, failed N.

Key Decisions

gh CLI handles authentication — no GITHUB_TOKEN env var required.
Username is derived at runtime from gh api user — no hardcoded config.
SSH clone URLs are used so no token is embedded in the remote URL.
Pagination ensures all forks are fetched beyond the 100-repo API limit.

Verification

Run gh auth status — confirm you are logged in.
Run the appropriate script for your OS (see Usage above).
Confirm repos are cloned or pulled in BASE_DIR.