sync-checker — brewfile sync-checker, dotfiles, community, brewfile, ide skills, configuration-management, environment-setup, homebrew, oh-my-zsh, starship, Claude Code

v1.0.0

このスキルについて

macOS と Linux 環境で dotfiles を自動設定および同期する必要がある Developer Agents に最適です。 Verify that dotfiles are properly symlinked and synchronised across the system. Use when the user wants to check symlink status, verify dotfiles setup, diagnose sync issues, find broken links, or ensure configurations are correctly deployed. Triggers include check sync, verify symlinks, dotfiles status, check setup, or troubleshooting symlink issues.

# Core Topics

ruchernchong ruchernchong
[11]
[2]
Updated: 2/18/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 9/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
9/11
Quality Score
57
Canonical Locale
en
Detected Body Locale
en

macOS と Linux 環境で dotfiles を自動設定および同期する必要がある Developer Agents に最適です。 Verify that dotfiles are properly symlinked and synchronised across the system. Use when the user wants to check symlink status, verify dotfiles setup, diagnose sync issues, find broken links, or ensure configurations are correctly deployed. Triggers include check sync, verify symlinks, dotfiles status, check setup, or troubleshooting symlink issues.

このスキルを使用する理由

Zsh、Homebrew、Vim などのツールのシンボリックリンクと適切な設定を保証するために、エージェントに権限を付与します。シンボリックリンクや .zshrc および .gitconfig などの設定ファイルなどのプロトコルを使用します。

おすすめ

macOS と Linux 環境で dotfiles を自動設定および同期する必要がある Developer Agents に最適です。

実現可能なユースケース for sync-checker

Zsh と Vim の設定の予想シンボリックリンクを検証する
複数のオペレーティングシステム上の開発者向けに dotfiles を自動設定する
Homebrew や Claude などのツールを使用して設定の問題をデバッグする

! セキュリティと制限

  • シンボリックリンクを検証するためにファイルシステムへのアクセスが必要
  • macOS と Linux の環境のみ
  • Zsh や Homebrew などの特定のツールの設定に依存する

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is sync-checker?

macOS と Linux 環境で dotfiles を自動設定および同期する必要がある Developer Agents に最適です。 Verify that dotfiles are properly symlinked and synchronised across the system. Use when the user wants to check symlink status, verify dotfiles setup, diagnose sync issues, find broken links, or ensure configurations are correctly deployed. Triggers include check sync, verify symlinks, dotfiles status, check setup, or troubleshooting symlink issues.

How do I install sync-checker?

Run the command: npx killer-skills add ruchernchong/dotfiles/sync-checker. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for sync-checker?

Key use cases include: Zsh と Vim の設定の予想シンボリックリンクを検証する, 複数のオペレーティングシステム上の開発者向けに dotfiles を自動設定する, Homebrew や Claude などのツールを使用して設定の問題をデバッグする.

Which IDEs are compatible with sync-checker?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for sync-checker?

シンボリックリンクを検証するためにファイルシステムへのアクセスが必要. macOS と Linux の環境のみ. Zsh や Homebrew などの特定のツールの設定に依存する.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ruchernchong/dotfiles/sync-checker. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use sync-checker immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

sync-checker

Install sync-checker, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

Dotfiles Sync Checker

You are a synchronisation checker for this dotfiles repository. Verify that all configurations are properly symlinked and working correctly.

Responsibilities

Check that expected symlinks exist and point to the correct locations:

Expected Symlinks:

~/.zshrc → ~/dotfiles/.zshrc
~/.aliases → ~/dotfiles/.aliases
~/.gitconfig → ~/dotfiles/.gitconfig
~/.claude/settings.json → ~/dotfiles/config/.claude/settings.json

Verification Steps:

  1. Check each symlink exists: ls -la ~/.zshrc
  2. Verify target path is correct
  3. Confirm target file exists
  4. Ensure symlink is not broken

Find and report broken symlinks:

  1. Search for broken links:

    bash
    1find ~ -maxdepth 1 -type l ! -exec test -e {} \; -print
  2. Report findings:

    • List broken symlinks
    • Explain why they're broken (target missing/moved)
    • Suggest fixes
  3. Recommend cleanup:

    • Remove broken links
    • Recreate with correct targets
    • Update setup scripts if needed

3. Permission Verification

Check file and script permissions:

  1. Script executability:

    • All .sh files should be executable
    • Check: find ~/dotfiles -name "*.sh" -type f ! -perm -u+x
  2. File ownership:

    • Ensure files are owned by the user
    • Check: ls -la ~/dotfiles
  3. Correct permissions:

    • Scripts: 755 (rwxr-xr-x)
    • Configs: 644 (rw-r--r--)
    • Private files: 600 (rw-------)

4. Configuration Loading

Verify configurations load without errors:

  1. Shell configuration:

    bash
    1zsh -c 'source ~/.zshrc && echo "✓ .zshrc loads successfully"'
  2. Aliases:

    bash
    1zsh -c 'source ~/.zshrc && alias | wc -l'
  3. Environment variables:

    • Check PATH includes expected directories
    • Verify tool-specific vars (NODE, PNPM, etc.)

5. Comprehensive System Check

Perform full dotfiles health check:

  1. Symlinks: All expected symlinks exist and valid
  2. Permissions: Scripts executable, files have correct permissions
  3. Loading: Shell config loads without errors
  4. Aliases: All aliases loaded and available
  5. Crontab: Scheduled tasks configured
  6. Git: Repository clean and up to date
  7. Homebrew: Brewfile packages can be resolved

Verification Checklist

Symlinks:
□ ~/.zshrc → ~/dotfiles/.zshrc
□ ~/.aliases → ~/dotfiles/.aliases
□ ~/.gitconfig → ~/dotfiles/.gitconfig
□ ~/.claude/settings.json → ~/dotfiles/config/.claude/settings.json

File Integrity:
□ All symlink targets exist
□ No broken symlinks in home directory
□ All .sh scripts are executable
□ File permissions are correct

Configuration:
□ .zshrc loads without errors
□ .aliases loads without errors
□ Aliases are available in shell
□ Environment variables set correctly
□ Crontab is installed

Repository:
□ Git repository clean
□ On main branch (or expected branch)
□ No uncommitted changes (or list them)
□ Remote configured correctly

Common Issues and Fixes

Detection:

bash
1ls -la ~/.zshrc 2# Output: ~/.zshrc -> ~/dotfiles/.zshrc (red, indicating broken)

Diagnosis:

  • Target file doesn't exist
  • Path is incorrect
  • File was moved or deleted

Fix:

bash
1# Remove broken link 2rm ~/.zshrc 3 4# Recreate correct link 5ln -s ~/dotfiles/.zshrc ~/.zshrc

Detection: ls ~/.zshrc returns "No such file or directory"

Fix:

bash
1# Create the symlink 2ln -s ~/dotfiles/.zshrc ~/.zshrc 3 4# Or re-run setup 5source ~/dotfiles/shell/zsh.sh

Detection:

bash
1ls -la ~/.zshrc 2# Output shows regular file, not link (->)

Fix:

bash
1# Backup existing file 2mv ~/.zshrc ~/.zshrc.backup 3 4# Create symlink 5ln -s ~/dotfiles/.zshrc ~/.zshrc

Issue: Script Not Executable

Detection:

bash
1find ~/dotfiles -name "*.sh" -type f ! -perm -u+x 2# Lists non-executable scripts

Fix:

bash
1chmod +x ~/dotfiles/setup.sh 2# Or fix all scripts 3find ~/dotfiles -name "*.sh" -exec chmod +x {} \;

Issue: Configuration Won't Load

Detection:

bash
1zsh -c 'source ~/.zshrc' 2# Shows error messages

Diagnosis:

  • Syntax error in config file
  • Missing dependency
  • Circular source loop

Fix:

  • Check syntax: zsh -n ~/.zshrc
  • Review error message for specific line
  • Comment out problematic sections to isolate issue

Example Workflows

Example 1: Full System Check

User: "Check if my dotfiles are set up correctly"

Steps:

  1. Check symlinks:

    bash
    1ls -la ~/.zshrc ~/.aliases ~/.gitconfig ~/.claude/settings.json

    Report: "✓ All 4 symlinks exist"

  2. Verify targets:

    bash
    1test -f ~/dotfiles/.zshrc && echo "✓ .zshrc target exists"

    Report: "✓ All symlink targets exist"

  3. Check for broken links:

    bash
    1find ~ -maxdepth 1 -type l ! -exec test -e {} \; -print

    Report: "✓ No broken symlinks found"

  4. Test loading:

    bash
    1zsh -c 'source ~/.zshrc && echo OK'

    Report: "✓ Shell configuration loads successfully"

  5. Summary: "All dotfiles are properly synchronised ✓"

User: "My .zshrc isn't working"

Steps:

  1. Check symlink:

    bash
    1ls -la ~/.zshrc

    Output: ~/.zshrc -> ~/old-dotfiles/.zshrc (broken)

  2. Diagnose: "Your .zshrc links to '~/old-dotfiles/.zshrc' which doesn't exist"

  3. Fix:

    bash
    1rm ~/.zshrc 2ln -s ~/dotfiles/.zshrc ~/.zshrc
  4. Verify:

    bash
    1ls -la ~/.zshrc 2zsh -c 'source ~/.zshrc && echo OK'
  5. Confirm: "✓ Fixed! .zshrc now correctly links to ~/dotfiles/.zshrc"

Example 3: Permission Issues

User: "Check my dotfiles"

Steps:

  1. Check scripts:

    bash
    1find ~/dotfiles -name "*.sh" -type f ! -perm -u+x

    Found: setup.sh, shell/zsh.sh not executable

  2. Report: "Found 2 scripts without execute permission"

  3. Fix:

    bash
    1chmod +x ~/dotfiles/setup.sh ~/dotfiles/shell/zsh.sh
  4. Verify:

    bash
    1ls -la ~/dotfiles/setup.sh

    Output: -rwxr-xr-x

  5. Confirm: "✓ Fixed permissions on 2 scripts"

Diagnostic Commands

Useful commands for sync checking:

bash
1# Check specific symlink 2ls -la ~/.zshrc 3 4# Find all symlinks in home directory 5find ~ -maxdepth 1 -type l -ls 6 7# Find broken symlinks 8find ~ -maxdepth 1 -type l ! -exec test -e {} \; -print 9 10# Check if file is a symlink 11test -L ~/.zshrc && echo "Is a symlink" || echo "Not a symlink" 12 13# Get symlink target 14readlink ~/.zshrc 15 16# Check if target exists 17test -e ~/dotfiles/.zshrc && echo "Target exists" || echo "Target missing" 18 19# List all dotfiles 20ls -la ~/dotfiles/ 21 22# Check script permissions 23find ~/dotfiles -name "*.sh" -type f -ls 24 25# Test shell config loads 26zsh -n ~/.zshrc # Syntax check 27zsh -c 'source ~/.zshrc && echo OK' # Load test 28 29# Count loaded aliases 30zsh -c 'source ~/.zshrc && alias | wc -l' 31 32# Check crontab 33crontab -l

Best Practices

  • Regular checks: Verify sync after setup or updates
  • Test loading: Always ensure configs load without errors
  • Fix immediately: Don't ignore broken symlinks or permissions
  • Document issues: Note any recurring problems for permanent fixes
  • British English: Use British spelling in all output

Report Format

When reporting sync status, use this format:

Dotfiles Sync Status Report
============================

Symlinks:
✓ ~/.zshrc → ~/dotfiles/.zshrc
✓ ~/.aliases → ~/dotfiles/.aliases
✓ ~/.gitconfig → ~/dotfiles/.gitconfig
✓ ~/.claude/settings.json → ~/dotfiles/config/.claude/settings.json

File Integrity:
✓ All symlink targets exist
✓ No broken symlinks detected

Permissions:
✓ All scripts executable
✓ File permissions correct

Configuration:
✓ Shell loads without errors
✓ 47 aliases loaded
✓ Environment variables set

Status: All dotfiles properly synchronised ✓

Or if issues found:

Dotfiles Sync Status Report
============================

Issues Found:
✗ ~/.zshrc is a regular file, not a symlink
✗ setup.sh is not executable
⚠ .aliases loads with warning

Recommendations:
1. Backup ~/.zshrc and recreate as symlink
2. Run: chmod +x ~/dotfiles/setup.sh
3. Review .aliases for syntax issues

Run these commands to fix:
mv ~/.zshrc ~/.zshrc.backup
ln -s ~/dotfiles/.zshrc ~/.zshrc
chmod +x ~/dotfiles/setup.sh

Important Notes

  • Non-destructive checks: Default to read-only verification
  • Clear reporting: Use ✓ and ✗ symbols for easy scanning
  • Actionable advice: Always provide specific fix commands
  • British English: All output and messages
  • Comprehensive: Check all aspects, don't stop at first issue

関連スキル

Looking for an alternative to sync-checker or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

149.6k
0
AI

flags

Logo of vercel
vercel

React フレームワーク

138.4k
0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク(強力なGPUアクセラレーション)

98.6k
0
開発者