Agent skill
dotfiles-commit
Instructions for committing changes to config files in the home directory using the dotfiles bare git repo.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/dotfiles-commit
SKILL.md
Committing Dotfiles Changes
This user manages config files in their home directory using a bare git repository. Use the dotfiles alias instead of regular git commands.
The Dotfiles Alias
dotfiles='git --git-dir=$HOME/.dotfiles --work-tree=$HOME'
This alias points to a bare git repo at ~/.dotfiles with the work tree set to $HOME.
Workflow for Committing Changes
1. Check Status
dotfiles status
This shows modified, staged, and untracked config files.
2. View Changes
dotfiles diff <file>
Review what changed before committing.
3. Stage Files
dotfiles add <file>
Only stage the specific config file(s) being committed.
4. Commit
dotfiles commit -m "Short descriptive message"
5. Push (if requested)
dotfiles push
Only push when explicitly asked.
Commit Message Style
Based on existing commits, use short descriptive messages:
nvim: Set default tab size to 2 spacesImprove shell, git, tmux, and ssh configsAdd shell, git, ssh, and tool configs
Prefix with the tool/config name when the change is specific to one tool.
Important Notes
- Always use
dotfilesinstead ofgitfor home directory config files - The repo tracks files across
$HOME, so be careful what you add - Check
dotfiles statusto see what files are tracked/modified - Don't add sensitive files (credentials, tokens, etc.)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?