chezmoi-sync
Interactive chezmoi drift check and sync. TRIGGERS - chezmoi sync, sync dotfiles, dotfile drift, chezmoi guard, chezmoi check.
Best use case
chezmoi-sync is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Interactive chezmoi drift check and sync. TRIGGERS - chezmoi sync, sync dotfiles, dotfile drift, chezmoi guard, chezmoi check.
Teams using chezmoi-sync should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/chezmoi-sync/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How chezmoi-sync Compares
| Feature / Agent | chezmoi-sync | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Interactive chezmoi drift check and sync. TRIGGERS - chezmoi sync, sync dotfiles, dotfile drift, chezmoi guard, chezmoi check.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Chezmoi Sync (Interactive) On-demand replacement for the automatic chezmoi stop guard. Run this skill whenever you want to check for chezmoi drift and sync tracked dotfiles. > **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues. ## Workflow ### Step 1: Check for drift Run `chezmoi status` and `chezmoi diff --no-pager` to detect drift between the source repo and home directory. ```bash chezmoi source-path && chezmoi status && echo "---" && chezmoi diff --no-pager | head -80 ``` If output is empty (no drift), report "Chezmoi is clean — no drift detected" and stop. ### Step 2: Present drift to user (AskUserQuestion) If drift exists, use `AskUserQuestion` to show the user what drifted and ask what to do. **Question 1** (header: "Drift action"): > "Chezmoi detected N drifted file(s): [list files]. What would you like to do?" Options: - **Sync all** — `chezmoi re-add` all drifted files, commit, and push - **Review each** — Walk through each file individually with per-file choices - **Ignore** — Skip sync, I'll handle it later ### Step 3a: Sync all (if chosen) ```bash chezmoi re-add --verbose chezmoi git -- add -A && chezmoi git -- commit -m "sync: dotfiles" && chezmoi git -- push chezmoi status # Verify clean ``` Report the commit hash and confirm clean state. ### Step 3b: Review each (if chosen) For each drifted file, use `AskUserQuestion`: **Question** (header: "File action"): > "[filename] has changed. What should we do?" Options: - **Sync** — Add this file to chezmoi source (`chezmoi add <path>`) - **Diff** — Show the full diff first, then ask again - **Forget** — Stop tracking this file (`chezmoi forget --force <path>`) - **Skip** — Leave it drifted for now After processing all files, if any were synced: ```bash chezmoi git -- add -A && chezmoi git -- commit -m "sync: dotfiles" && chezmoi git -- push ``` ### Step 3c: Ignore (if chosen) Report: "Skipped chezmoi sync. Run `/dotfiles-tools:chezmoi-sync` when ready." ## Notes - Always use `chezmoi forget --force` (not bare `forget`) to avoid TTY prompt issues - The chezmoi source dir is `~/own/dotfiles` (configured in `~/.config/chezmoi/chezmoi.toml`) ## Post-Execution Reflection After this skill completes, reflect before closing the task: 0. **Locate yourself.** — Find this SKILL.md's canonical path before editing. 1. **What failed?** — Fix the instruction that caused it. 2. **What worked better than expected?** — Promote to recommended practice. 3. **What drifted?** — Fix any script, reference, or dependency that no longer matches reality. 4. **Log it.** — Evolution-log entry with trigger, fix, and evidence. Do NOT defer. The next invocation inherits whatever you leave behind.
Related Skills
chezmoi-workflows
Dotfile backup and sync with chezmoi. TRIGGERS - chezmoi, dotfiles, sync dotfiles, backup configs, cross-machine sync.
voice-quality-audition
Audition Kokoro TTS voices to compare quality and grade. TRIGGERS - audition voices, kokoro voices, voice comparison, tts voice, voice quality, compare voices.
settings-and-tuning
Configure TTS voices, speed, timeouts, queue depth, and bot settings. TRIGGERS - configure tts, change voice, tts speed, queue depth, tts timeout, bot config, tune settings, adjust parameters.
full-stack-bootstrap
One-time bootstrap for Kokoro TTS engine, Telegram bot, and BotFather setup. TRIGGERS - setup tts, install kokoro, botfather, bootstrap tts-tg-sync, configure telegram bot, full stack setup.
diagnostic-issue-resolver
Diagnose and resolve TTS and Telegram bot issues. TRIGGERS - tts not working, bot not responding, kokoro error, audio not playing, lock stuck, telegram bot troubleshoot, diagnose issue.
component-version-upgrade
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro, clean tts, teardown, component removal.
send-message
Use when user wants to send a text message on Telegram as their personal account via MTProto, text someone, or message a contact by username, phone, or chat ID.
send-media
Use when user wants to send or upload a file, photo, video, voice note, or document on Telegram via their personal account.
search-messages
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.
pin-message
Use when user wants to pin or unpin a message in a Telegram chat, group, or channel, or manage pinned messages.
mark-read
Use when user wants to mark Telegram chats as read, clear unread badges and mentions, dismiss notifications, or acknowledge messages to remove the unread counter.