Skip to content

feat: introduce diagnostics context and prompt #1167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

gennaro-tedesco
Copy link

I often find myself wanting to resolve the code diagnostics and manually adding the corresponding error messages and/or buffers to the chat, together with a custom prompt. I thought I could propose to add diagnostics as default context and prompt that the user can select in order to streamline this process.

This PR introduces:

  • context: workspace diagnostics for all open buffers
  • prompts: instructions for the model to patch each single one independently

@jellydn jellydn force-pushed the diagnostics_context branch from e2a736a to 3c59d03 Compare July 12, 2025 00:20
@deathbeam
Copy link
Collaborator

tools branch already has diagnostics as separate function, and also for opened buffers. This PR is also adding diagnostics for current buffer only and not workspace diagnostics, check vim.diagnostic.get() documentation

@gennaro-tedesco
Copy link
Author

Good morning and thank you for reviewing the PR!

For me to better understand: you are saying there is a tools branch that already superseds these changes?

@deathbeam
Copy link
Collaborator

Yea pretty much

@gennaro-tedesco
Copy link
Author

Ah, very well, then we can close this PR I guess.

P. S. I don't see the tools branch (I wanted to install it) - is it the canary branch or which one?

@jellydn
Copy link
Contributor

jellydn commented Jul 15, 2025

That's on open PRs on this repo @gennaro-tedesco, fyi.

@gennaro-tedesco
Copy link
Author

Fantastic, thank you for the great work! I will close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants