fix(prompt): update role syntax in multi-msg prompt for consistency

[sahdev77]

Description here... Help the reviewer by:

• linking to an issue that includes more details

Checklist (if applicable):

• PR title is following https://www.conventionalcommits.org/en/v1.0.0/
• Tested (manually, unit tested, etc.)
• Docs updated (updated docs or a docs bug required)

[gemini-code-assist]

Summary of Changes

Hello @sahdev77, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a minor but important consistency issue within the prompt definitions. It updates the role syntax in a sample multi-message prompt file, replacing an older templating style with a newer, standardized format. This ensures that all prompt definitions adhere to a uniform syntax, improving readability and maintainability for developers working with these prompts.

Highlights

• Prompt Syntax Update: The syntax for defining roles (system and user) within the multi-msg.prompt sample file has been updated to ensure consistency with the new <<<dotprompt:role:...>>> format.
• Consistency Improvement: This change standardizes the prompt role definition, moving from the older {{ role "..." }} syntax to the more current <<<dotprompt:role:...>>> syntax.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the role syntax in go/samples/prompts/prompts/multi-msg.prompt to the <<<dotprompt:role:...>>> format for consistency. The change is correct and improves standardization. However, I've identified that TestMultiMessagesPrompt in go/ai/prompt_test.go still utilizes the old {{ role "..." }} syntax. I recommend updating this test to use the new syntax to ensure complete test coverage and maintain consistency across the codebase. It would also be valuable to verify if other samples and tests in the repository, including those for other languages, need a similar update.

[MichaelDoyle]

This is not correct; {{role: "user"}} is indeed the correct/expected syntax. There are bug(s) in message rendering that make it appear that {{role: "user"}} is not supported.