Claude-skill-registry keybind-audit
Analyze keybindings across all dotfiles for conflicts, duplicates, and inconsistencies. Use when modifying keybindings or checking for conflicts.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/keybind-audit" ~/.claude/skills/majiayu000-claude-skill-registry-keybind-audit && rm -rf "$T"
manifest:
skills/data/keybind-audit/SKILL.mdsource content
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 | | |
| tmux | | , |
| vim | | , , , |
| neovim | | , |
| neovim plugins | | , keymaps in setup() |
| obsidian | | , , |
| alacritty | | |
Analysis checklist
-
Cross-tool conflicts: Same key combo, different behavior across tools
- Focus on: Ctrl+key, Alt+key, leader combinations
- Example:
in tmux vs zsh<C-g>
-
Duplicates: Same keybinding defined multiple times within one tool
- Example:
in both dot_vimrc and nvim/lua/keymap.luaj -> gj
- Example:
-
Consistency: Check vim-style navigation unity
- Are hjkl mapped consistently?
- Is
pattern consistent?<leader>fj/fk/fl
-
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
- ...