diff --git a/packages/core/commands/pr/fix.md b/packages/core/commands/pr/fix.md
index 846b05e..311a0ac 100644
--- a/packages/core/commands/pr/fix.md
+++ b/packages/core/commands/pr/fix.md
@@ -32,13 +32,18 @@ $ARGUMENTS
 
 <%~ include("@align-pr-branch", { action: "analyzing repository files or making code changes for this PR", scope: "inspect or modify local code for this PR" }) %>
 
+### Load Changes
+
+Call `changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <active-branch>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
+
 ### Analyze Feedback
 
 Separate true course corrections from noise or already-resolved feedback:
 1. Review `<pr-context.threads>` for open, unresolved conversations
 2. Check `<pr-context.reviews>` for state changes (CHANGES_REQUESTED, etc.)
-3. Prioritize critical issues (bugs, security, broken contracts)
-4. Identify which files need changes
+3. Use `<changes>` to understand the current PR diff before deciding what to adjust
+4. Prioritize critical issues (bugs, security, broken contracts)
+5. Identify which files need changes
 
 Do not blindly follow every suggestion—some may lead you off course.
 
diff --git a/packages/core/commands/pr/review.md b/packages/core/commands/pr/review.md
index f590e0e..3f56f9d 100644
--- a/packages/core/commands/pr/review.md
+++ b/packages/core/commands/pr/review.md
@@ -37,7 +37,7 @@ If `<pr-context.pr.body>` links to exactly one clear ticket:
 
 ### Load Changes
 
-Call `changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <pr-context.pr.headRefName>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
+Call `changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <active-branch>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
 
 ### Review Changes
 
diff --git a/packages/opencode/.opencode/commands/pr/fix.md b/packages/opencode/.opencode/commands/pr/fix.md
index dcb2539..0a118cc 100644
--- a/packages/opencode/.opencode/commands/pr/fix.md
+++ b/packages/opencode/.opencode/commands/pr/fix.md
@@ -50,13 +50,18 @@ $ARGUMENTS
 - If checkout fails, STOP and report that the PR branch could not be checked out locally
 - Do not inspect or modify local code for this PR until `<active-branch>` equals `<pr-branch>`
 
+### Load Changes
+
+Call `kompass_changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <active-branch>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
+
 ### Analyze Feedback
 
 Separate true course corrections from noise or already-resolved feedback:
 1. Review `<pr-context.threads>` for open, unresolved conversations
 2. Check `<pr-context.reviews>` for state changes (CHANGES_REQUESTED, etc.)
-3. Prioritize critical issues (bugs, security, broken contracts)
-4. Identify which files need changes
+3. Use `<changes>` to understand the current PR diff before deciding what to adjust
+4. Prioritize critical issues (bugs, security, broken contracts)
+5. Identify which files need changes
 
 Do not blindly follow every suggestion—some may lead you off course.
 
diff --git a/packages/opencode/.opencode/commands/pr/review.md b/packages/opencode/.opencode/commands/pr/review.md
index b02fa71..c75e39e 100644
--- a/packages/opencode/.opencode/commands/pr/review.md
+++ b/packages/opencode/.opencode/commands/pr/review.md
@@ -59,7 +59,7 @@ If `<pr-context.pr.body>` links to exactly one clear ticket:
 
 ### Load Changes
 
-Call `kompass_changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <pr-context.pr.headRefName>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
+Call `kompass_changes_load` with `base: <pr-context.pr.baseRefName>`, `head: <active-branch>`, and `depthHint: <pr-context.pr.commitCount>` only when it is a positive integer. Store as `<changes>`.
 
 ### Review Changes