sync-checker

Verify dotfile symlinks and report synchronization issues with remediation guidance.

12|3|Updated Jun 5, 2017
One-click install
npx skills add https://github.com/ruchernchong/dotfiles --skill sync-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-checker
Source: https://github.com/ruchernchong/dotfiles/tree/main/.claude/skills/sync-checker
Command: npx skills add https://github.com/ruchernchong/dotfiles --skill sync-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuration drift and broken symlinks can silently corrupt a development environment, leading to frustrating debugging sessions and inconsistent setups across machines. This Skill proactively identifies and resolves these issues, ensuring your environment remains stable.

Core Features & Use Cases

  • Symlink Verification: Confirms that all critical dotfile symlinks (e.g., .zshrc, .gitconfig) exist and correctly point to their intended targets within your dotfiles repository.
  • Broken Link Detection: Scans your home directory to find and report any broken symlinks, explaining why they're broken and suggesting immediate fixes.
  • Permission Verification: Ensures that all your dotfile scripts have executable permissions and that configuration files have correct ownership, preventing "permission denied" errors.
  • Use Case: After a system update, a manual configuration change, or when onboarding a new machine, run this Skill to quickly verify that all your dotfiles are correctly symlinked, permissions are set, and configurations load, preventing unexpected issues and ensuring a consistent setup.

Quick Start

Check if my dotfiles are properly synchronised and report any issues.

Frequently Asked Questions about sync-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my dotfiles are properly symlinked?

Symlink verification confirms that all critical dotfile symlinks exist and correctly point to their intended targets within your dotfiles repository. Run this Skill to scan your home directory, detect broken links, and identify misaligned configurations causing environment drift.

What causes broken symlinks in my dotfiles configuration?

Broken symlinks occur when symlinks point to deleted or moved targets, often after system updates, manual configuration changes, or machine migrations. This Skill identifies broken links, explains why they're broken, and suggests immediate fixes to restore your environment.

How do I verify dotfile permissions and ownership are correct?

Permission verification ensures dotfile scripts have executable permissions and configuration files have correct ownership. This prevents permission-denied errors and validates that shell and tool settings load correctly across your system.

Can I detect configuration drift after a system update?

Yes. After a system update or manual configuration change, run this Skill to quickly verify all dotfiles are correctly symlinked, permissions are set, and configurations load, preventing unexpected issues and ensuring consistent setup.

Why should I verify dotfiles when onboarding a new machine?

New machine setups often have incomplete or misaligned dotfile deployments. Verification confirms symlinks exist, detects broken links, validates permissions, and reports overall health with remediation guidance before environment problems surface.