What
Three plugins that complement the existing setup with zero overlap against already-installed plugins.
1. nvim-treesitter-context
Repo: https://github.com/nvim-treesitter/nvim-treesitter-context
Shows the current function/class/block header as a sticky line at the top of the window while scrolling through long files.
Rationale tied to existing config: The config already has a custom scopeline.lua that draws treesitter-based scope brackets at the cursor position, and snacks.nvim indent chunks. nvim-treesitter-context complements both by keeping the enclosing scope name visible at the top of the buffer while scrolling — the gap these two don't fill. It uses the same treesitter queries already installed via TSSync, so there's no extra grammar dependency.
2. todo-comments.nvim
Repo: https://github.com/folke/todo-comments.nvim
Highlights TODO, FIXME, HACK, NOTE, BUG, WARN comment markers with distinct colors and provides a quickfix list of all such markers in the project.
Rationale tied to existing config: The config uses quickfix heavily: :Compile populates it, <leader>co/<leader>cc open/close it, and quicker.nvim improves its UI. todo-comments.nvim adds a :TodoQuickFix command that integrates directly into this workflow. Its fzf integration (:TodoFzfLua) also slots into the existing fzf-lua setup via <leader>/.
3. vim-illuminate
Repo: https://github.com/RRethy/vim-illuminate
Highlights other occurrences of the word under the cursor using LSP references, treesitter, or regex fallback.
Rationale tied to existing config: With multiple LSPs active (pyright, pyrefly, clangd, ts_ls, rust_analyzer, gopls) and tiny-inline-diagnostic.nvim already providing rich inline diagnostics, the visual feedback loop is strong — but there's no "where else is this symbol used?" highlight. vim-illuminate fills that gap using the already-attached LSP clients for accuracy. It respects vim.diagnostic settings and works alongside blink.cmp without conflict.
Non-suggestions
nvim-spectre and lazygit.nvim were considered but skipped: grug-far.nvim is already suggested in #287 for search/replace, and fugitive.vim + diffview.nvim + gitsigns.nvim cover the git workflow well enough.
What
Three plugins that complement the existing setup with zero overlap against already-installed plugins.
1. nvim-treesitter-context
Repo: https://github.com/nvim-treesitter/nvim-treesitter-context
Shows the current function/class/block header as a sticky line at the top of the window while scrolling through long files.
Rationale tied to existing config: The config already has a custom
scopeline.luathat draws treesitter-based scope brackets at the cursor position, andsnacks.nvimindent chunks.nvim-treesitter-contextcomplements both by keeping the enclosing scope name visible at the top of the buffer while scrolling — the gap these two don't fill. It uses the same treesitter queries already installed viaTSSync, so there's no extra grammar dependency.2. todo-comments.nvim
Repo: https://github.com/folke/todo-comments.nvim
Highlights
TODO,FIXME,HACK,NOTE,BUG,WARNcomment markers with distinct colors and provides a quickfix list of all such markers in the project.Rationale tied to existing config: The config uses quickfix heavily:
:Compilepopulates it,<leader>co/<leader>ccopen/close it, andquicker.nvimimproves its UI.todo-comments.nvimadds a:TodoQuickFixcommand that integrates directly into this workflow. Its fzf integration (:TodoFzfLua) also slots into the existingfzf-luasetup via<leader>/.3. vim-illuminate
Repo: https://github.com/RRethy/vim-illuminate
Highlights other occurrences of the word under the cursor using LSP references, treesitter, or regex fallback.
Rationale tied to existing config: With multiple LSPs active (pyright, pyrefly, clangd, ts_ls, rust_analyzer, gopls) and
tiny-inline-diagnostic.nvimalready providing rich inline diagnostics, the visual feedback loop is strong — but there's no "where else is this symbol used?" highlight.vim-illuminatefills that gap using the already-attached LSP clients for accuracy. It respectsvim.diagnosticsettings and works alongsideblink.cmpwithout conflict.Non-suggestions
nvim-spectreandlazygit.nvimwere considered but skipped:grug-far.nvimis already suggested in #287 for search/replace, andfugitive.vim+diffview.nvim+gitsigns.nvimcover the git workflow well enough.