Agent skill
sync-gruvbox-theme
Verify and sync gruvbox theme consistency across vim, neovim, tmux, and terminal
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/sync-gruvbox-theme-bfowle-dotfiles
SKILL.md
Sync Gruvbox Theme
This skill ensures the gruvbox theme is consistently configured across all tools.
Task
You should:
-
Check gruvbox configuration in:
- Neovim (
nvim/lua/plugins/gruvbox.lua) - Vim (
vim/vimrc.ln) - Tmux (
tmux/tmux.conf.ln) - Bash/terminal settings (
bash/bashrc.ln)
- Neovim (
-
Verify all use the same variant (dark/light)
-
Check color settings:
- 256 color support
- True color (RGB) support
- Terminal overrides
-
Ensure consistent appearance of:
- Background colors
- Foreground text
- Syntax highlighting
- Status lines
- Borders/separators
-
Suggest improvements for better consistency
Files to Check
Neovim
nvim/lua/plugins/gruvbox.lua- should use ellisonleao/gruvbox.nvim- Check contrast setting (hard/soft/default)
- Verify colorscheme is set
Vim
vim/vimrc.ln- should have gruvbox colorscheme- Background setting (dark/light)
Tmux
tmux/tmux.conf.ln- should use egel/tmux-gruvbox plugin- Verify @tmux-gruvbox setting matches vim/neovim
- Check terminal-overrides for true color
Bash
bash/bashrc.ln- check TERM variable- Verify LSCOLORS or LS_COLORS use gruvbox palette
Validation
Test by:
- Opening neovim and checking
:colorscheme - Running tmux and verifying status bar colors
- Listing files with
lsand checking colors - Opening vim and verifying theme
Common Issues
- Terminal doesn't support 256 colors
- True color not enabled in tmux
- Mismatched dark/light variants
- Missing gruvbox plugins
- Wrong TERM environment variable
Output
Report:
- Current theme variant in each tool
- Any inconsistencies found
- Color support status (256/true color)
- Recommended fixes
- Commands to apply fixes
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?