How do I install the Workflow Dotfiles Sync skill?

Run npx skillmds@latest add lev-os/workflow-dotfiles-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workflow Dotfiles Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflow Dotfiles Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflow Dotfiles Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workflow Dotfiles Sync?

lev-os (@lev-os) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflow Dotfiles Sync by lev-os — Agent Skill

Name: Workflow Dotfiles Sync
Rating: 4.2 (5 reviews)
Author: lev-os

File contents

Workflow: Dotfiles Sync

NEVER REBASE. ALWAYS MERGE.

Terminology

Term	Meaning	Path
local	The actual dotfiles on this machine (chezmoi target)	`$HOME/.<file>`
remote	The chezmoi source repo, git-tracked and pushed	`$HOME/.local/share/chezmoi`

Always use "local" and "remote" when presenting drift reports. Never use chezmoi's internal "source/target" terminology in user-facing output.

Trigger

Run this workflow when you need to:

reconcile local-vs-remote dotfile drift
inspect pending chezmoi changes before apply
promote intentional local changes back into remote
perform a safe remote-first sync across machines

Inputs

Chezmoi remote repo at $HOME/.local/share/chezmoi
Local state under $HOME
dotfiles helper available on PATH
Optional handoff context in .lev/pm/handoffs/

Steps

Run dotfiles status and dotfiles sync.
Classify results into:
- remote-only change (exists in remote, not reflected locally)
- local-only intentional drift (local changed, remote is stale)
- same-area conflict (both changed)
- runtime noise (volatile files, timestamps, caches)
Resolve intent into remote first:
- remote-only wins automatically UNLESS the local removal was intentional (ask)
- local-only intentional drift gets promoted to remote via chezmoi re-add
- same-area conflicts must pause and escalate
If remote changed:
- review git -C ~/.local/share/chezmoi status --short
- commit
- fetch, then merge remote changes
- push
Only after remote is settled:
- run chezmoi apply --force on the chosen local set
Re-run dotfiles sync to verify the remaining drift is only expected runtime noise or clean.

Team

Role	Responsibility
dotfiles operator	Reads `dotfiles` planner output, classifies drift, and updates remote
git reconciler	Commits, pulls, pushes the chezmoi remote repo once intent is resolved
escalation agent	Opens AgentPing or human review when same-area conflicts exist

Outputs

Updated chezmoi remote repo state
Updated local home state after apply
Dry-run report at ~/.local/state/lev/dotfiles-sync-plan.latest.txt
Optional handoff updates documenting decisions and escalation points

Validation

dotfiles sync completes without mutating state and produces a current report
Any committed remote changes are pushed successfully
chezmoi apply --force completes only after remote is reconciled
Same-area conflicts are escalated, never auto-merged
Final dotfiles status reflects either clean state or explicitly accepted runtime noise

---name: workflow-dotfiles-syncdescription: Use when reconciling chezmoi local-vs-remote drift, reviewing pending machine-state changes, or performing safe remote-first dotfiles sync across machines.---# Workflow: Dotfiles SyncNEVER REBASE. ALWAYS MERGE.## Terminology| Term | Meaning | Path ||------|---------|------|| **local** | The actual dotfiles on this machine (chezmoi target) | `$HOME/.<file>` || **remote** | The chezmoi source repo, git-tracked and pushed | `$HOME/.local/share/chezmoi` |Always use "local" and "remote" when presenting drift reports. Never use chezmoi's internal "source/target" terminology in user-facing output.## TriggerRun this workflow when you need to:- reconcile local-vs-remote dotfile drift- inspect pending chezmoi changes before apply- promote intentional local changes back into remote- perform a safe remote-first sync across machines## Inputs- Chezmoi remote repo at `$HOME/.local/share/chezmoi`- Local state under `$HOME`- `dotfiles` helper available on PATH- Optional handoff context in `.lev/pm/handoffs/`## Steps1. Run `dotfiles status` and `dotfiles sync`.2. Classify results into: - remote-only change (exists in remote, not reflected locally) - local-only intentional drift (local changed, remote is stale) - same-area conflict (both changed) - runtime noise (volatile files, timestamps, caches)3. Resolve intent into remote first: - remote-only wins automatically UNLESS the local removal was intentional (ask) - local-only intentional drift gets promoted to remote via `chezmoi re-add` - same-area conflicts must pause and escalate4. If remote changed: - review `git -C ~/.local/share/chezmoi status --short` - commit - fetch, then merge remote changes - push5. Only after remote is settled: - run `chezmoi apply --force` on the chosen local set6. Re-run `dotfiles sync` to verify the remaining drift is only expected runtime noise or clean.## Team| Role | Responsibility ||------|---------------|| dotfiles operator | Reads `dotfiles` planner output, classifies drift, and updates remote || git reconciler | Commits, pulls, pushes the chezmoi remote repo once intent is resolved || escalation agent | Opens AgentPing or human review when same-area conflicts exist |## Outputs- Updated chezmoi remote repo state- Updated local home state after apply- Dry-run report at `~/.local/state/lev/dotfiles-sync-plan.latest.txt`- Optional handoff updates documenting decisions and escalation points## Validation- `dotfiles sync` completes without mutating state and produces a current report- Any committed remote changes are pushed successfully- `chezmoi apply --force` completes only after remote is reconciled- Same-area conflicts are escalated, never auto-merged- Final `dotfiles status` reflects either clean state or explicitly accepted runtime noise

Frequently asked questions

Workflow Dotfiles Sync