context master task

[okuvshynov]

Examples:

• https://docs.cursor.com/context/@-symbols/basic
• https://sourcegraph.com/docs/cody/capabilities/chat
• https://tabby.tabbyml.com/blog/2023/10/16/repository-context-for-code-completion/

Let's try to combine various options of context retrieval for effective processing by local LLMs:

1. embeddings
2. non-ML code indexing tools (e.g. ctags, treesitter)
3. code history (pull requests, commits, etc.) - how the code changed and why
4. tool-based - let LLM call some tool to get needed context.

Currently it's being done within the vimqq plugin, but a better way would be to decouple the context provider, run it in background, similar to vim gutentags.

Current state:

• [x] selection
• [x] git blame -- appears very important
• [x] ctags
• [x] file
• [x] entire project
• github issues/PRs -- in progress now
• [ ] treesitter
• [ ] other LSP-based
• [ ] embeddings
• [ ] tool-based

[okuvshynov]

We also need to easily select multiple files and ask to modify them. For example:

"refactor https://github.com/okuvshynov/vimqq/blob/5100d9154f7d85eabd418dea68946b808e1787d1/tests/test_log.sh and https://github.com/okuvshynov/vimqq/blob/5100d9154f7d85eabd418dea68946b808e1787d1/tests/test_qq.sh and extract common functionality"

[okuvshynov]

So many new plugins, let's check what are their context options:

• https://github.com/yetone/avante.nvim
• https://github.com/continuedev/continue
• https://sourcegraph.com/docs/cody/core-concepts/context
• https://docs.continue.dev/chat/context-selection

[okuvshynov]

based on some experimentation we need to be able to add multiple files as a context, with wildcards (e.g. -f bots/*.vim)