How do I install the Managing Dotfiles skill?

Run npx skillmds add majiayu000/managing-dotfiles-2 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 Dotfiles safe to use?

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

Which AI agents work with Managing Dotfiles?

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

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

Who published Managing Dotfiles?

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

Managing Dotfiles by majiayu000 — Agent Skill

Name: Managing Dotfiles
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Dotfiles Management with GNU Stow

Manage dotfiles tracked in ~/.claude/dotfiles/ using GNU Stow — a symlink farm manager that mirrors directory structure from a source package into $HOME.

Directory Convention

Each package under dotfiles/ mirrors the home directory structure:

dotfiles/
├── tmux/.config/tmux/tmux.conf    →  ~/.config/tmux/tmux.conf
├── git/.gitconfig                 →  ~/.gitconfig
├── nvim/.config/nvim/init.lua     →  ~/.config/nvim/init.lua
└── zsh/.zshrc                     →  ~/.zshrc

The package name (e.g. tmux, git) is just an organizational label. The internal directory structure determines where symlinks land.

Adding a New Package

Three steps:

# 1. Create the package directory mirroring $HOME structure
mkdir -p ~/.claude/dotfiles/<pkg>/<path-relative-to-home>

# 2. Move the existing config into the package
mv ~/<path-to-config> ~/.claude/dotfiles/<pkg>/<path-relative-to-home>/

# 3. Stow to create the symlink
stow -d ~/.claude/dotfiles -t ~ <pkg>

Example — adding starship config:

mkdir -p ~/.claude/dotfiles/starship/.config
mv ~/.config/starship.toml ~/.claude/dotfiles/starship/.config/starship.toml
stow -d ~/.claude/dotfiles -t ~ starship

Common Commands

# Stow a package (create symlinks)
stow -d ~/.claude/dotfiles -t ~ <pkg>

# Unstow a package (remove symlinks)
stow -d ~/.claude/dotfiles -t ~ -D <pkg>

# Re-stow (unstow + stow, useful after restructuring)
stow -d ~/.claude/dotfiles -t ~ -R <pkg>

# Dry run (see what would happen without doing it)
stow -d ~/.claude/dotfiles -t ~ -n -v <pkg>

# Stow all packages at once
make dotfiles

Installing Stow

# macOS
brew install stow

# Debian/Ubuntu
apt install stow

# Fedora/RHEL
dnf install stow

Troubleshooting

Conflict: existing target is not a symlink

Stow won't overwrite real files. Use --adopt to pull the existing file into the package, then stow:

stow -d ~/.claude/dotfiles -t ~ --adopt <pkg>

Warning: --adopt replaces the package file with the existing target file. If your package version is newer, back it up first or use git diff after adopting.

Conflict: target is a symlink managed by another package

Two stow packages can't own the same target path. Check which package owns it:

ls -la <conflicting-path>

Then decide which package should own the file and remove the duplicate.

Stow created a directory symlink instead of file symlinks

Stow uses "tree folding" — if a package is the only owner of a directory, it symlinks the directory itself rather than individual files. This is usually fine. If you need file-level symlinks (e.g., because the directory has other non-stowed files), use --no-folding:

stow -d ~/.claude/dotfiles -t ~ --no-folding <pkg>

---name: managing-dotfiles-2description: Manage dotfiles tracked in ~/.claude/dotfiles/ using GNU Stow. Use when adding config files to dotfiles, stowing/unstowing packages, or troubleshooting symlink conflicts.--- # Dotfiles Management with GNU Stow Manage dotfiles tracked in `~/.claude/dotfiles/` using GNU Stow — a symlink farm manager that mirrors directory structure from a source package into `$HOME`. ## Directory Convention Each package under `dotfiles/` mirrors the home directory structure: ```text dotfiles/ ├── tmux/.config/tmux/tmux.conf → ~/.config/tmux/tmux.conf ├── git/.gitconfig → ~/.gitconfig ├── nvim/.config/nvim/init.lua → ~/.config/nvim/init.lua └── zsh/.zshrc → ~/.zshrc ``` The package name (e.g. `tmux`, `git`) is just an organizational label. The internal directory structure determines where symlinks land. ## Adding a New Package Three steps: ```bash # 1. Create the package directory mirroring $HOME structure mkdir -p ~/.claude/dotfiles/<pkg>/<path-relative-to-home> # 2. Move the existing config into the package mv ~/<path-to-config> ~/.claude/dotfiles/<pkg>/<path-relative-to-home>/ # 3. Stow to create the symlink stow -d ~/.claude/dotfiles -t ~ <pkg> ``` Example — adding starship config: ```bash mkdir -p ~/.claude/dotfiles/starship/.config mv ~/.config/starship.toml ~/.claude/dotfiles/starship/.config/starship.toml stow -d ~/.claude/dotfiles -t ~ starship ``` ## Common Commands ```bash # Stow a package (create symlinks) stow -d ~/.claude/dotfiles -t ~ <pkg> # Unstow a package (remove symlinks) stow -d ~/.claude/dotfiles -t ~ -D <pkg> # Re-stow (unstow + stow, useful after restructuring) stow -d ~/.claude/dotfiles -t ~ -R <pkg> # Dry run (see what would happen without doing it) stow -d ~/.claude/dotfiles -t ~ -n -v <pkg> # Stow all packages at once make dotfiles ``` ## Installing Stow ```bash # macOS brew install stow # Debian/Ubuntu apt install stow # Fedora/RHEL dnf install stow ``` ## Troubleshooting ### Conflict: existing target is not a symlink Stow won't overwrite real files. Use `--adopt` to pull the existing file into the package, then stow: ```bash stow -d ~/.claude/dotfiles -t ~ --adopt <pkg> ``` **Warning**: `--adopt` replaces the package file with the existing target file. If your package version is newer, back it up first or use `git diff` after adopting. ### Conflict: target is a symlink managed by another package Two stow packages can't own the same target path. Check which package owns it: ```bash ls -la <conflicting-path> ``` Then decide which package should own the file and remove the duplicate. ### Stow created a directory symlink instead of file symlinks Stow uses "tree folding" — if a package is the only owner of a directory, it symlinks the directory itself rather than individual files. This is usually fine. If you need file-level symlinks (e.g., because the directory has other non-stowed files), use `--no-folding`: ```bash stow -d ~/.claude/dotfiles -t ~ --no-folding <pkg> ```

Frequently asked questions