Added Gemini Enterprise System Instructions#344
Added Gemini Enterprise System Instructions#344BarrenWardo wants to merge 4 commits intox1xhlol:mainfrom
Conversation
WalkthroughAdded three new enterprise guidance documents defining Gemini Enterprise chat behavior, multi-agent orchestration with delegate agents and transfer semantics, contextual information usage (time/location/profile), tool-invocation formatting, and a title-generation specification. No code or public API signatures were changed. Changes
Sequence Diagram(s)mermaid Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: Repository UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (1)📓 Common learnings🪛 LanguageToolGoogle/Gemini/Enterprise/Gemini-2.5-Flash.md[style] ~12-~12: Unless you want to emphasize “not”, use “cannot” which is more common. (CAN_NOT_PREMIUM) [uncategorized] ~12-~12: Did you mean the formatting language “Markdown” (= proper noun)? (MARKDOWN_NNP) [uncategorized] ~19-~19: Did you mean the formatting language “Markdown” (= proper noun)? (MARKDOWN_NNP) [style] ~23-~23: To elevate your writing, try using a synonym here. (HARD_TO) [grammar] ~25-~25: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) [grammar] ~26-~26: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [style] ~29-~29: Consider using a more formal alternative. (MORE_INFO) [style] ~31-~31: Consider using a less common alternative to make your writing sound more unique and professional. (FEEL_FREE_TO_STYLE_ME) [grammar] ~31-~31: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [style] ~31-~31: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase. (EN_WEAK_ADJECTIVE) [grammar] ~32-~32: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [grammar] ~32-~32: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [style] ~41-~41: This phrase is redundant. Consider writing “facts”. (ESTABLISHED_FACT2) [grammar] ~61-~61: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [grammar] ~62-~62: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [grammar] ~62-~62: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [style] ~63-~63: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE) [grammar] ~70-~70: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [grammar] ~81-~81: Use a hyphen to join words. (QB_NEW_EN_HYPHEN) [style] ~86-~86: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym. (ENGLISH_WORD_REPEAT_BEGINNING_RULE) [grammar] ~94-~94: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) [style] ~144-~144: In American English, abbreviations like “etc.” require a period. (ETC_PERIOD) [uncategorized] ~145-~145: Did you mean the formatting language “Markdown” (= proper noun)? (MARKDOWN_NNP) 🪛 markdownlint-cli2 (0.18.1)Google/Gemini/Enterprise/Gemini-2.5-Flash.md40-40: Unordered list indentation (MD007, ul-indent) 41-41: Unordered list indentation (MD007, ul-indent) 42-42: Unordered list indentation (MD007, ul-indent) 43-43: Unordered list indentation (MD007, ul-indent) 48-48: Heading levels should only increment by one level at a time (MD001, heading-increment) 50-50: Unordered list indentation (MD007, ul-indent) 51-51: Unordered list indentation (MD007, ul-indent) 52-52: Unordered list indentation (MD007, ul-indent) 53-53: Unordered list indentation (MD007, ul-indent) 54-54: Unordered list indentation (MD007, ul-indent) 55-55: Unordered list indentation (MD007, ul-indent) 56-56: Unordered list indentation (MD007, ul-indent) 57-57: Unordered list indentation (MD007, ul-indent) 61-61: Unordered list indentation (MD007, ul-indent) 62-62: Unordered list indentation (MD007, ul-indent) 63-63: Unordered list indentation (MD007, ul-indent) 72-72: Emphasis used instead of a heading (MD036, no-emphasis-as-heading) 🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @Google/Gemini/Enterprise/Gemini-2.5-Flash.md:
- Line 26: Fix the pronoun mismatch in the sentence that currently reads
"indicate what I was able to help with" by changing it to "indicate what you
were able to help with" so the instruction maintains the second-person framing
used elsewhere; keep the rest of the line that instructs to use first-person
pronouns and to refer to yourself as "Gemini Enterprise" intact.
📜 Review details
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
Google/Gemini/Enterprise/Gemini-2.5-Flash.mdGoogle/Gemini/Enterprise/Gemini-2.5-Pro.mdGoogle/Gemini/Enterprise/Title-Generator.txt
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.064Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.
🪛 LanguageTool
Google/Gemini/Enterprise/Gemini-2.5-Flash.md
[style] ~12-~12: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...o so. * For Code related questions: You can not execute code, you can only show code to...
(CAN_NOT_PREMIUM)
[uncategorized] ~12-~12: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...e, you can only show code to users with markdown format. When code execution is required...
(MARKDOWN_NNP)
[uncategorized] ~19-~19: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...them for conversation. * ALWAYS use markdown in your answers. You can make use of mu...
(MARKDOWN_NNP)
[style] ~23-~23: To elevate your writing, try using a synonym here.
Context: ...o blocks of texts that are too long and hard to read. * If a user will ask a questio...
(HARD_TO)
[grammar] ~25-~25: Ensure spelling is correct
Context: ...on by asking them questions back. Do so particulary when the prompt is unclear or ambiguous...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~26-~26: Use a hyphen to join words.
Context: ...hen answering a prompt, try to use first person pronouns to refer to yourself and...
(QB_NEW_EN_HYPHEN)
[style] ~29-~29: Consider using a more formal alternative.
Context: ..., use available agents and tools to get more information, then only ask for clarifications if a ...
(MORE_INFO)
[style] ~31-~31: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...e, start each section with a heading. * Feel free to add an emoji to each section heading if...
(FEEL_FREE_TO_STYLE_ME)
[grammar] ~31-~31: Use a hyphen to join words.
Context: ...ing if it makes sense and it is not tone deaf. For section headings render them a...
(QB_NEW_EN_HYPHEN)
[style] ~31-~31: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...eadings. Do not do this if the topic is very serious. * In general, do not use bullet poin...
(EN_WEAK_ADJECTIVE)
[grammar] ~32-~32: Use a hyphen to join words.
Context: .... For instance, for comparison, for step by step instructions, etc. * Separate ne...
(QB_NEW_EN_HYPHEN)
[grammar] ~32-~32: Use a hyphen to join words.
Context: ...or instance, for comparison, for step by step instructions, etc. * Separate new s...
(QB_NEW_EN_HYPHEN)
[style] ~41-~41: This phrase is redundant. Consider writing “facts”.
Context: ...u MUST actively integrate and reference established facts, decisions, and user preferences from o...
(ESTABLISHED_FACT2)
[grammar] ~61-~61: Use a hyphen to join words.
Context: ...ation * User location: the current IP based user location is redacted. If th...
(QB_NEW_EN_HYPHEN)
[grammar] ~62-~62: Use a hyphen to join words.
Context: ...r's time or time zone do not used the IP based location since it can be coming fr...
(QB_NEW_EN_HYPHEN)
[grammar] ~62-~62: Use a hyphen to join words.
Context: ...e the above user's current time and user preferred timezone even when the questio...
(QB_NEW_EN_HYPHEN)
[style] ~63-~63: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ion implies a location like "here". * If the user most probably wants a geo-loca...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~70-~70: Use a hyphen to join words.
Context: ...om the recent (last few days-weeks) work related interactions of the user. Think ...
(QB_NEW_EN_HYPHEN)
[grammar] ~81-~81: Use a hyphen to join words.
Context: ... their work context. Personal Profile Based Disambiguation As an assistant, ...
(QB_NEW_EN_HYPHEN)
[style] ~86-~86: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...st relevant to the personal profile. 3. In the final answer acknowledge the disamb...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~94-~94: Ensure spelling is correct
Context: ...ation) *Email: redacted Additional websearch information: Biography Summary: U...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~144-~144: In American English, abbreviations like “etc.” require a period.
Context: ... (.pdf, .png, .csv, .txt, .pptx, .docx, etc) 2. File-like content or any content th...
(ETC_PERIOD)
[uncategorized] ~145-~145: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...at has to be parsed by code (e.g., as a markdown table, list, or plain text) are implici...
(MARKDOWN_NNP)
Google/Gemini/Enterprise/Gemini-2.5-Pro.md
[uncategorized] ~12-~12: “Google” is a proper noun and needs to be capitalized.
Context: ...tence in the response which refers to a google search result MUST end with a citation,...
(A_GOOGLE)
[grammar] ~28-~28: Use a hyphen to join words.
Context: ...ess to the location and returns location relevant results. ```python def brows...
(QB_NEW_EN_HYPHEN)
[grammar] ~49-~49: Use a hyphen to join words.
Context: .... You can also access to a set of 3rd party APIs listed further below. Each ca...
(QB_NEW_EN_HYPHEN)
[style] ~69-~69: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...o so. * For Code related questions: You can not execute code, you can only show code to...
(CAN_NOT_PREMIUM)
[uncategorized] ~69-~69: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...e, you can only show code to users with markdown format. When code execution is required...
(MARKDOWN_NNP)
[uncategorized] ~76-~76: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...them for conversation. * ALWAYS use markdown in your answers. You can make use of mu...
(MARKDOWN_NNP)
[style] ~80-~80: To elevate your writing, try using a synonym here.
Context: ...o blocks of texts that are too long and hard to read. * If a user will ask a questio...
(HARD_TO)
[grammar] ~82-~82: Ensure spelling is correct
Context: ...on by asking them questions back. Do so particulary when the prompt is unclear or ambiguous...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~83-~83: Use a hyphen to join words.
Context: ...hen answering a prompt, try to use first person pronouns to refer to yourself and...
(QB_NEW_EN_HYPHEN)
[style] ~86-~86: Consider using a more formal alternative.
Context: ..., use available agents and tools to get more information, then only ask for clarifications if a ...
(MORE_INFO)
[style] ~88-~88: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...e, start each section with a heading. * Feel free to add an emoji to each section heading if...
(FEEL_FREE_TO_STYLE_ME)
[grammar] ~88-~88: Use a hyphen to join words.
Context: ...ing if it makes sense and it is not tone deaf. For section headings render them a...
(QB_NEW_EN_HYPHEN)
[style] ~88-~88: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...eadings. Do not do this if the topic is very serious. * In general, do not use bullet poin...
(EN_WEAK_ADJECTIVE)
[grammar] ~89-~89: Use a hyphen to join words.
Context: .... For instance, for comparison, for step by step instructions, etc. * Separate ne...
(QB_NEW_EN_HYPHEN)
[grammar] ~89-~89: Use a hyphen to join words.
Context: ...or instance, for comparison, for step by step instructions, etc. * Separate new s...
(QB_NEW_EN_HYPHEN)
[style] ~98-~98: This phrase is redundant. Consider writing “facts”.
Context: ...u MUST actively integrate and reference established facts, decisions, and user preferences from o...
(ESTABLISHED_FACT2)
[grammar] ~118-~118: Use a hyphen to join words.
Context: ...ation * User location: the current IP based user location is redacted. If th...
(QB_NEW_EN_HYPHEN)
[grammar] ~119-~119: Use a hyphen to join words.
Context: ...r's time or time zone do not used the IP based location since it can be coming fr...
(QB_NEW_EN_HYPHEN)
[grammar] ~119-~119: Use a hyphen to join words.
Context: ...e the above user's current time and user preferred timezone even when the questio...
(QB_NEW_EN_HYPHEN)
[style] ~120-~120: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ion implies a location like "here". * If the user most probably wants a geo-loca...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~127-~127: Use a hyphen to join words.
Context: ...om the recent (last few days-weeks) work related interactions of the user. Think ...
(QB_NEW_EN_HYPHEN)
[grammar] ~138-~138: Use a hyphen to join words.
Context: ... their work context. Personal Profile Based Disambiguation As an assistant, ...
(QB_NEW_EN_HYPHEN)
[style] ~143-~143: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...st relevant to the personal profile. 3. In the final answer acknowledge the disamb...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~151-~151: Ensure spelling is correct
Context: ...ation) *Email: redacted Additional websearch information: Biography Summary: U...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[uncategorized] ~159-~159: Do not mix variants of the same word (‘fulfill’ and ‘fulfil’) within a single text.
Context: ...delegates them to specialized agents to fulfill the user's request. ". You have a lis...
(EN_EXACT_COHERENCY_RULE)
[style] ~201-~201: In American English, abbreviations like “etc.” require a period.
Context: ... (.pdf, .png, .csv, .txt, .pptx, .docx, etc) 2. File-like content or any content th...
(ETC_PERIOD)
[uncategorized] ~202-~202: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...at has to be parsed by code (e.g., as a markdown table, list, or plain text) are implici...
(MARKDOWN_NNP)
🪛 markdownlint-cli2 (0.18.1)
Google/Gemini/Enterprise/Gemini-2.5-Flash.md
24-24: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
25-25: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
26-26: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
97-97: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
100-100: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
105-105: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
107-107: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
108-108: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
109-109: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
110-110: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
111-111: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
112-112: Unordered list indentation
Expected: 4; Actual: 6
(MD007, ul-indent)
113-113: Unordered list indentation
Expected: 4; Actual: 6
(MD007, ul-indent)
114-114: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
118-118: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
119-119: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
120-120: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
129-129: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (3)
Google/Gemini/Enterprise/Gemini-2.5-Pro.md (1)
1-221: System prompt preserved; no changes recommended.Per the repository's convention, reverse-engineered system prompts are preserved exactly as extracted, including any unusual formatting. This file documents comprehensive Gemini Enterprise guidance covering tool execution, agent orchestration (root_agent delegating to imagen_agent, videogen_agent, docgen_agent, and file_and_coding_agent), multi-turn conversation handling, and contextual information management. The structure and delegation semantics are clear.
One minor note: Line 82 contains "particulary" which appears to be a spelling variant. If this is a transcription artifact rather than intentional prompt material, it may be worth confirming with the source. Otherwise, preserve as-is per repository standards.
Google/Gemini/Enterprise/Gemini-2.5-Flash.md (1)
1-164: High content overlap with Gemini-2.5-Pro.md warrants clarification.Gemini-2.5-Flash.md shares ~75% structural and textual overlap with Gemini-2.5-Pro.md. Flash is a shorter variant that omits the initial tool_code execution guidelines, browse function details, and API access instructions from the Pro version, starting directly with the enterprise chat persona.
Confirm whether two nearly-identical files are intentional (e.g., different deployment contexts) or a merge/duplication artifact. If intentional, consider documenting the rationale; if not, consolidate to a single source of truth.
Google/Gemini/Enterprise/Title-Generator.txt (1)
1-41: Well-structured title generator specification; approved.Clear and concise definition of the sidebar title generator's role, instructions, and output constraints. The five examples effectively illustrate scope, edge cases (handling non-contextual filenames like "123.txt"), and integration with multi-turn conversation history. Output format rules are specific and actionable (under 30 chars, important words first, no data structure wrapping). Aligns well with the broader enterprise guidance in sibling documents.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
2 participants
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.