Menu
Manage dotfiles tracked in ~/.claude/dotfiles/ using GNU Stow. Use when adding config files to dotfiles, stowing/unstowing packages, or troubleshooting symlink conflicts.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.
Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.
Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.
Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").
| name | managing-dotfiles |
| description | Manage dotfiles tracked in ~/.claude/dotfiles/ using GNU Stow. Use when adding config files to dotfiles, stowing/unstowing packages, or troubleshooting symlink conflicts. |
Manage dotfiles tracked in ~/.claude/dotfiles/ using GNU Stow — a symlink farm manager that mirrors directory structure from a source package into $HOME.
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.
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
# 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
# macOS
brew install stow
# Debian/Ubuntu
apt install stow
# Fedora/RHEL
dnf install stow
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.
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 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>