ReddRadar
Agent skill
keybind-audit
Analyze keybindings across all dotfiles for conflicts, duplicates, and inconsistencies. Use when modifying keybindings or checking for conflicts.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/devops/keybind-audit
SKILL.md
Keybind Audit
Analyze keybindings across all configuration files in this dotfiles repository.
When to use
- User wants to add or modify a keybinding
- User asks about keybinding conflicts
- User wants to check consistency across tools
Target files
| Tool | File | Pattern |
|---|---|---|
| zsh | dot_zshrc.tmpl |
bindkey |
| tmux | dot_tmux.conf |
bind, bind-key |
| vim | dot_vimrc |
nnoremap, vnoremap, inoremap, cnoremap |
| neovim | dot_config/nvim/lua/keymap.lua |
vim.keymap.set, nvim_set_keymap |
| neovim plugins | dot_config/nvim/lua/plugin_configs/*.lua |
vim.keymap.set, keymaps in setup() |
| obsidian | dot_obsidian.vimrc |
nmap, vmap, exmap |
| alacritty | dot_config/alacritty/alacritty.toml |
[[keyboard.bindings]] |
Analysis checklist
-
Cross-tool conflicts: Same key combo, different behavior across tools
- Focus on: Ctrl+key, Alt+key, leader combinations
- Example:
<C-g>in tmux vs zsh
-
Duplicates: Same keybinding defined multiple times within one tool
- Example:
j -> gjin both dot_vimrc and nvim/lua/keymap.lua
- Example:
-
Consistency: Check vim-style navigation unity
- Are hjkl mapped consistently?
- Is
<leader>fj/fk/flpattern consistent?
-
Shadowed defaults: Overwritten important defaults that may cause confusion
-
Dead bindings: Commented-out bindings that might be worth revisiting
Output format
Group by severity:
Conflicts (must fix)
- Key:
<C-x> - Tools: tmux (kill-pane) vs zsh (execute)
- Recommendation: ...
Duplicates (should fix)
- Key:
j -> gj - Files: dot_vimrc:1, keymap.lua:9
- Recommendation: Keep only in keymap.lua
Inconsistencies (consider)
- ...
Info
- ...
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
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?