Skip to content

fix: load PR change context from the active branch #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dbpolito merged 1 commit into from
Apr 16, 2026
Merged

fix: load PR change context from the active branch #97

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions packages/core/commands/pr/fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion packages/core/commands/pr/review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
9 changes: 7 additions & 2 deletions packages/opencode/.opencode/commands/pr/fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion packages/opencode/.opencode/commands/pr/review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading