Replies: 1 comment
-
This is an awesome suggestion. I'm currently reworking Tools. These allow you to A help tool would be a brilliant idea. We could share a list of help docs available to the LLM and let it decide what it would like to consume. I do have a My main focus is to add a tool which can update a buffer next if a user gives approval. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Neovim and high-quality plugins are shipped with well-structured docs in doc/*.txt.
This documentation is indexed with tags and easily searchable (e.g.,
Telescope help_tags
).I think that a useful slash-command could be
/help
which triggers something likeTelescope help_tags
and inserts the selected documentation section in that chat.Another approach is the one used by VSCode: it uses
@
-commands to provide context across multiple files. Right now, three@
-commands are implemented:@workspace
@terminal
@vscode
For example, the prompt
will use the VSCode docs to perform RAG.
However, I think that this second option (e.g.,
@neovim
) is not straightforward and it would only make sense to reconsider if embeddings (and how to use them) will be supported in the future by codecompanion.nvimBeta Was this translation helpful? Give feedback.
All reactions