Shared Prompt Fragment

Summary

Each configured repository can store one shared prompt fragment: free-form organization guidance that gets injected identically into every reviewer agent's prompt for that repository, without editing each agent's own persona prompt.

The fragment is metadata on CodeRepository.ReviewConfiguration (CodeRepositoryReviewConfiguration.SharedPromptFragment), alongside the existing repository-level file filter and check-run settings. It is empty by default.

Editing the Fragment

On the Manage Agents page, the toolbar next to the repository picker has a Shared prompt button (alongside File filters and New agent) that opens a slideover with a Markdown editor. Saving persists the fragment through the same repository-configuration save endpoint used for file filters, so it round-trips with the rest of CodeRepositoryReviewConfiguration.

Prompt Injection

CodeReviewPromptBuilder renders the fragment into an <organization_guidance> block in the shared, reviewer-neutral prompt body — the same body broadcast identically to every reviewer agent in a run. An empty fragment renders a self-closing <organization_guidance /> tag.

This applies to both review paths:

• GitHub pull request reviews, via CodeReviewExecutionContext.ToPromptInput.
• MCP uploaded-diff reviews (expert_code_review), via ExpertCodeReviewRunner, when the uploaded diff's repository is mapped to a configured Zeeq repository. Unmapped repositories run without a shared guidance fragment, consistent with how mapped library names are handled for that path.

Data Flow

User edits fragment in Shared prompt slideover
  -> store saves it as part of CodeRepositoryReviewConfiguration
  -> next review run loads the repository's ReviewConfiguration
  -> CodeReviewPromptBuilder renders <organization_guidance> into the shared prompt body
  -> every active reviewer agent for the run receives the same guidance