How do I install the Managing Chezmoi skill?

Run npx skillmds@latest add mrpointer/managing-chezmoi 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 Managing Chezmoi safe to use?

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

Which AI agents work with Managing Chezmoi?

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 Managing Chezmoi free to use?

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

Who published Managing Chezmoi?

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

Managing Chezmoi by mrpointer — Agent Skill

Name: Managing Chezmoi
Author: mrpointer

Managing Chezmoi

Manage dotfiles with chezmoi. Use whenever editing or reviewing chezmoi source files in this repo, including `dot_*`, `private_dot_*`, `dot_config/`, `private_dot_config/`, `.chezmoitemplates/`, `.chezmoiignore`, and `*.tmpl`; adding files to chezmoi; validating source changes with status/diff/dry-run; debugging source/target mapping or missing changes; or asking how a dotfile is managed. In sandboxed agent work, validate with diff/dry-run and do not run write-capable `chezmoi apply` or `--force`. For command uncertainties, use Context7.

mrpointer b59682f 3 files · 7.8 KB Updated Sep 17, 2026

File contents

Chezmoi Management

Operate as a chezmoi power-user: understand source/target model, CLI workflows, templating, ignore rules, and drift resolution.

Quick Reference

Commands & workflows: See commands-and-workflows.md Troubleshooting: See troubleshooting.md

Sandbox Policy

This repo is edited from inside a nono sandbox. Treat chezmoi source files as the deliverable: do not run commands that write target files, including final chezmoi apply, targeted non-dry-run applies, or --force. Validate with chezmoi diff, chezmoi apply --dry-run -v, source review, and git diff. If the user wants changes applied to $HOME, give them the exact command to run outside the sandbox instead of running it here.

Default Workflow

Confirm source ownership: before editing a file under ~, use chezmoi source-path <target> or inspect whether the source uses dot_*, private_dot_*, dot_config/, private_dot_config/, or a template source
Inspect state: use chezmoi status and chezmoi diff for managed targets; use git diff for repo-only files that chezmoi does not manage as targets
Edit source directly: modify files in this repo (the source state)
Validate safely: run chezmoi diff and chezmoi apply --dry-run -v for managed targets; stop at source review and git diff for unmanaged repo files
Verify: chezmoi verify after larger refactors when it can run without writing target files

Complexity Decision Tree

Situation	Action
Simple file change	Edit source → `chezmoi diff` → `chezmoi apply --dry-run -v`
New file to manage	`chezmoi add <target>` → inspect source → `chezmoi apply --dry-run -v`
Unexpected diffs	`chezmoi diff -v` → `chezmoi apply --dry-run -v` → troubleshoot
Conditional behavior	Check templates + `chezmoi data`
Repo-only file	Edit source → review source → `git diff`
Command uncertainty	Fetch docs via Context7

Chezmoi Expertise Checklist

When helping with a request, consider:

Source vs target: User might be editing the wrong side
Managed config files: For target config under ~/.config, look for matching dot_config/ or private_dot_config/ source before editing the target
Source file naming: dot_ prefixes, private_ files, .tmpl suffix
Ignore rules: .chezmoiignore patterns and conditionals
Templates: {{ ... }} logic, chezmoi data
Safe operations: Prefer dry-runs, source review, and diffs; source edits plus validation are the goal in this sandbox

Context7 Usage

When uncertain about chezmoi commands/flags or version-specific behavior:

Call resolve-library-id with libraryName="chezmoi"
Call query-docs with a targeted question
Prefer newest documented behavior

---name: managing-chezmoidescription: Manage dotfiles with chezmoi. Use whenever editing or reviewing chezmoi source files in this repo, including `dot_*`, `private_dot_*`, `dot_config/`, `private_dot_config/`, `.chezmoitemplates/`, `.chezmoiignore`, and `*.tmpl`; adding files to chezmoi; validating source changes with status/diff/dry-run; debugging source/target mapping or missing changes; or asking how a dotfile is managed. In sandboxed agent work, validate with diff/dry-run and do not run write-capable `chezmoi apply` or `--force`. For command uncertainties, use Context7.---# Chezmoi ManagementOperate as a chezmoi power-user: understand source/target model, CLI workflows, templating, ignore rules, and drift resolution.## Quick Reference**Commands & workflows:** See [commands-and-workflows.md](references/commands-and-workflows.md)**Troubleshooting:** See [troubleshooting.md](references/troubleshooting.md)## Sandbox PolicyThis repo is edited from inside a nono sandbox. Treat chezmoi source files as the deliverable: do not run commands that write target files, including final `chezmoi apply`, targeted non-dry-run applies, or `--force`. Validate with `chezmoi diff`, `chezmoi apply --dry-run -v`, source review, and git diff. If the user wants changes applied to `$HOME`, give them the exact command to run outside the sandbox instead of running it here.## Default Workflow1. **Confirm source ownership**: before editing a file under `~`, use `chezmoi source-path <target>` or inspect whether the source uses `dot_*`, `private_dot_*`, `dot_config/`, `private_dot_config/`, or a template source2. **Inspect state**: use `chezmoi status` and `chezmoi diff` for managed targets; use `git diff` for repo-only files that chezmoi does not manage as targets3. **Edit source directly**: modify files in this repo (the source state)4. **Validate safely**: run `chezmoi diff` and `chezmoi apply --dry-run -v` for managed targets; stop at source review and git diff for unmanaged repo files5. **Verify**: `chezmoi verify` after larger refactors when it can run without writing target files## Complexity Decision Tree| Situation | Action ||-----------|--------|| Simple file change | Edit source → `chezmoi diff` → `chezmoi apply --dry-run -v` || New file to manage | `chezmoi add <target>` → inspect source → `chezmoi apply --dry-run -v` || Unexpected diffs | `chezmoi diff -v` → `chezmoi apply --dry-run -v` → troubleshoot || Conditional behavior | Check templates + `chezmoi data` || Repo-only file | Edit source → review source → `git diff` || Command uncertainty | Fetch docs via Context7 |## Chezmoi Expertise ChecklistWhen helping with a request, consider:- **Source vs target**: User might be editing the wrong side- **Managed config files**: For target config under `~/.config`, look for matching `dot_config/` or `private_dot_config/` source before editing the target- **Source file naming**: `dot_` prefixes, `private_` files, `.tmpl` suffix- **Ignore rules**: `.chezmoiignore` patterns and conditionals- **Templates**: `{{ ... }}` logic, `chezmoi data`- **Safe operations**: Prefer dry-runs, source review, and diffs; source edits plus validation are the goal in this sandbox## Context7 UsageWhen uncertain about chezmoi commands/flags or version-specific behavior:1. Call `resolve-library-id` with `libraryName="chezmoi"`2. Call `query-docs` with a targeted question3. Prefer newest documented behavior

Frequently asked questions