You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sends PR/issue/autolink context to review mode input
Adds context to all review mode prompts. Gathers cached-only PR/issue/autolink context based on the review entrypoint, and passes into the prompt to help the agent understant intent behind changes. Goal is to improve review quality.
template: `You are an expert code reviewer analyzing a set of code changes. Your goal is to identify meaningful issues — bugs, logic errors, security vulnerabilities, missing error handling, and potential regressions — while ignoring style preferences and linter-level concerns. Focus on problems a careful human reviewer would catch.
534
534
535
535
Examine the following code changes in Git diff format. Each non-header line inside a hunk has been annotated with its 1-based new-file line number in a \`[NNNNN]\` block placed immediately after the line-type marker (\` \`, \`+\`, or \`-\`):
@@ -546,6 +546,9 @@ Author's description of the changes:
546
546
\${message}
547
547
</~~message~~>
548
548
549
+
Related work items (known pull requests and issues for this change set). Use these for *intent*: what the change is trying to accomplish. They are not authoritative spec — if a finding contradicts the stated intent, flag it rather than defer to it. May be empty.
550
+
\${context}
551
+
549
552
Produce a structured review in the following XML format. Include ONLY the XML tags described — no other text:
550
553
551
554
<overview>
@@ -580,7 +583,7 @@ Review the changes and produce the structured XML output above.`,
template: `You are an expert code reviewer performing an initial assessment of a set of code changes. You are given a file manifest (not full diffs) — use the file paths, change types, and line counts to identify which areas deserve closer inspection.
585
588
586
589
File manifest (JSON array of changed files):
@@ -593,6 +596,9 @@ Author's description of the changes:
593
596
\${message}
594
597
</~~message~~>
595
598
599
+
Related work items (known pull requests and issues for this change set). Use these for *intent* — what the change is trying to accomplish — when ranking which areas deserve closer review. May be empty.
600
+
\${context}
601
+
596
602
Produce a structured assessment in the following XML format. Include ONLY the XML tags described — no other text:
597
603
598
604
<overview>
@@ -619,7 +625,7 @@ Assess the changes and produce the structured XML output above.`,
template: `You are an expert code reviewer performing a detailed inspection of specific files that were flagged for closer review. You have the context from an initial overview assessment.
624
630
625
631
Initial overview of the full changeset:
@@ -634,6 +640,9 @@ Author's description of the changes:
634
640
\${message}
635
641
</~~message~~>
636
642
643
+
Related work items (known pull requests and issues for this change set). Use these for *intent* — what the change is trying to accomplish. They are not authoritative spec; if a finding contradicts the stated intent, flag it. May be empty.
644
+
\${context}
645
+
637
646
Code changes for the files in this focus area (Git diff format). Each non-header line inside a hunk has been annotated with its 1-based new-file line number in a \`[NNNNN]\` block placed immediately after the line-type marker (\` \`, \`+\`, or \`-\`):
638
647
\` [ 42] context line\` // context: exists in both old and new; number = new-file line
639
648
\`+[ 43] added line\` // added: only in new file; number = new-file line
0 commit comments