Automated summary
Pulls the latest configuration from a GitHub repository and automatically merges local and synced settings for Claude.
Strengths
- Automates updating Claude configuration from GitHub
- Intelligently merges synced and local settings without loss
- Handles local changes by stashing them before the pull
- Provides a summary of changes made
Limitations
- Requires prior setup (Git repository and remote) to work
- Can fail due to merge conflicts or network issues
- Only works within the Claude Code environment
Use this command when you want to sync your Claude configuration with the latest version from your GitHub repository.
Avoid using it if you haven't configured the Git repository yet or if you prefer to manage configurations manually.
Security analysis
SafeThe skill runs non-destructive git and bash commands to pull configuration from a user's own GitHub repository and merge settings. It does not use curl, rm, or exfiltration, and relies on user-configured repositories and pre-existing scripts. No obfuscation or disabling of safety features is present.
No concerns found
How this analysis is madeExamples
/claude-github-sync:pullname: pull description: Pull latest configuration from GitHub
Pull Configuration
Pull the latest configuration from your GitHub repository and automatically merge settings.
Usage
/claude-github-sync:pull
Configuration Reference
| Item | Path | Description |
|------|------|-------------|
| Config file | ~/.claude/sync-config.json | Sync configuration (repo URL, setup method) |
| Git remote | ~/.claude/.git/config | Primary check - git origin remote URL |
| Sync settings | ~/.claude/settings.sync.json | Shared settings (synced to GitHub) |
| Local settings | ~/.claude/settings.local.json | Machine-specific settings (gitignored) |
| Merged output | ~/.claude/settings.json | Auto-merged result of sync + local |
| Merge script | ~/.claude/scripts/merge-settings.mjs | Deep merges sync + local → settings.json |
Instructions
Step 1: Check git remote (primary check)
The sync is configured if ~/.claude has a git remote. Config file (~/.claude/sync-config.json) is optional fallback.
cd ~/.claude
# Primary check: git remote
REPO_URL=$(git remote get-url origin 2>/dev/null)
if [ -n "$REPO_URL" ]; then
echo "✅ Remote: $REPO_URL"
else
# Fallback: check config file
CONFIG_FILE="$HOME/.claude/sync-config.json"
if [ -f "$CONFIG_FILE" ]; then
echo "⚠️ Config exists but no git remote"
echo "Run: /claude-github-sync:setup to fix"
exit 1
else
echo "❌ Not configured"
echo ""
echo "Run: /claude-github-sync:setup"
exit 1
fi
fi
Step 2: Pull changes
cd ~/.claude
# Get current branch
BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "main")
# Save current HEAD for change detection
HEAD_BEFORE=$(git rev-parse HEAD 2>/dev/null)
# Stash local changes if any
STASHED=false
if ! git diff --quiet 2>/dev/null; then
echo "Stashing local changes..."
git stash
STASHED=true
fi
# Pull with rebase
if git pull --rebase origin "$BRANCH" 2>&1; then
echo "✅ Pulled latest configuration"
else
echo "❌ Pull failed"
echo ""
echo "Possible issues:"
echo " - Network connection"
echo " - Merge conflicts (run: git status)"
echo " - Remote branch doesn't exist"
git status --short
fi
# Restore stashed changes
if [ "$STASHED" = true ]; then
echo "Restoring local changes..."
git stash pop
fi
# Show what changed
HEAD_AFTER=$(git rev-parse HEAD 2>/dev/null)
if [ "$HEAD_BEFORE" != "$HEAD_AFTER" ]; then
echo ""
echo "📋 Changes pulled:"
echo ""
echo "--- New commits ---"
git log --oneline "$HEAD_BEFORE..$HEAD_AFTER"
echo ""
echo "--- Files changed ---"
git diff --stat "$HEAD_BEFORE..$HEAD_AFTER"
else
echo ""
echo "📋 No new changes from remote."
fi
Step 3: Merge settings
After pulling, automatically merge sync and local settings.
The merge script can be in multiple locations:
~/.claude/scripts/merge-settings.mjs(user installed)- Plugin's scripts directory (bundled)
cd ~/.claude
# Find merge script in multiple locations
MERGE_SCRIPT=""
# Location 1: User's scripts directory
if [ -f "$HOME/.claude/scripts/merge-settings.mjs" ]; then
MERGE_SCRIPT="$HOME/.claude/scripts/merge-settings.mjs"
fi
# Location 2: Plugin cache (find latest version)
if [ -z "$MERGE_SCRIPT" ]; then
PLUGIN_SCRIPT=$(find "$HOME/.claude/plugins/cache/claude-sync/claude-github-sync" -name "merge-settings.mjs" 2>/dev/null | head -1)
if [ -n "$PLUGIN_SCRIPT" ]; then
MERGE_SCRIPT="$PLUGIN_SCRIPT"
fi
fi
# Location 3: Marketplace source
if [ -z "$MERGE_SCRIPT" ]; then
MARKETPLACE_SCRIPT="$HOME/.claude/plugins/marketplaces/claude-sync/scripts/merge-settings.mjs"
if [ -f "$MARKETPLACE_SCRIPT" ]; then
MERGE_SCRIPT="$MARKETPLACE_SCRIPT"
fi
fi
# Run merge if found
if [ -n "$MERGE_SCRIPT" ]; then
echo ""
echo "Merging settings..."
node "$MERGE_SCRIPT"
else
echo ""
echo "⚠️ merge-settings.mjs not found"
echo " Settings will not be auto-merged"
fi
Step 4: Report result
Show the user what was updated.
echo ""
echo "📊 Current settings files:"
ls -la ~/.claude/settings*.json 2>/dev/null | awk '{print " " $9 " (" $5 " bytes)"}'
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pull-configuration-from-github-mma3js3r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pull-configuration-from-github-mma3js3r/download' --output '.skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md.part' && mv '.skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md.part' '.skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md' && test -s '.skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pull' && cp -R '.skill-downloads/pull-configuration-from-github-mma3js3r' '.claude/skills/pull'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pull-configuration-from-github-mma3js3r'openskills read 'pull-configuration-from-github-mma3js3r'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pull-configuration-from-github-mma3js3r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.