chore(compass-assistant): improved instructions prompt COMPASS-9811 #7303
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the conversation instructions prompt for the Compass Assistant by replacing a simple instruction string with a comprehensive, structured prompt that clearly defines the assistant's capabilities and limitations.
- Replaced basic instruction comment with detailed structured prompt
- Added explicit sections for instructions, abilities, and inabilities
- Clarified the assistant's scope regarding UI-specific vs general MongoDB questions
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]>
gagik
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Got this as a suggestion from @mongodben. It immediately and obviously performs better. We'll follow this up with some eval cases that test this specifically, but I just want to get it in in the meantime since it is such a huge improvement.