Expand PR Review to consider a linked issue in the PR Body

[strawgate]

If there is a linked issue that the PR fixes or resolves, let's also instruct the model to take the issue into account.

[github-actions]

2 related issues

• Update PR Body Workflow #216 — it introduced the PR body update workflow, which is the source this issue wants PR review to additionally consider.
• update-pr-body needs issues: read #249 — it documents issues: read permission needs in the PR body workflow, which is directly relevant when adding linked-issue context to review.

---

What is this? | From workflow: Duplicate Issue Detector

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

tl;dr: This request is already implemented in the PR Review workflow prompt, so I recommend closing this as already addressed (or narrowing to a specific edge case if behavior was observed to miss links).

Recommendation

No implementation change is required for pr-review today: the prompt already instructs the agent to read linked issues from the PR body before reviewing.
If you want to harden behavior, a small follow-up could explicitly enumerate additional link formats (for example Resolves #123 and full GitHub issue URLs), but that is an enhancement rather than a gap.

Findings

• In .github/workflows/gh-aw-pr-review.md:116, Step 1 explicitly states: if PR description references issues (example: Fixes #123, Closes #456), call issue_read for each linked issue.
• The compiled workflow contains the same instruction at .github/workflows/gh-aw-pr-review.lock.yml:539, confirming this is active in the shipped workflow, not just source markdown.
• The docs-focused variant also has equivalent issue-link handling (.github/workflows/gh-aw-docs-pr-review.md:129).
• I did not find a prior issue in this repo specifically reporting this exact gap; issue search results were mostly unrelated.

Verification

I verified the current repository state with targeted code search:

$ rg -n "references issues|``Fixes #123``|``Closes #456``|issue_read" .github/workflows/*pr-review*
.github/workflows/gh-aw-pr-review.md:116:3. If the PR description references issues (e.g., "``Fixes #123``", "``Closes #456``"), call `issue_read` ...
.github/workflows/gh-aw-pr-review.lock.yml:539:          3. If the PR description references issues (e.g., "``Fixes #123``", "``Closes #456``"), call `issue_read` ...
.github/workflows/gh-aw-docs-pr-review.md:129:3. If the PR description references issues (e.g., "``Fixes #123``", "``Closes #456``"), call `issue_read` ...

Detailed Action Plan

1. Close this issue as already implemented, referencing .github/workflows/gh-aw-pr-review.md:116 and .github/workflows/gh-aw-pr-review.lock.yml:539.
2. (Optional enhancement) Update the wording in .github/workflows/gh-aw-pr-review.md:116 to explicitly include additional patterns such as Resolves #... and full issue URLs.
3. Run make compile to regenerate lock files if prompt text changes.
4. Confirm the compiled prompt still includes the updated instruction in .github/workflows/gh-aw-pr-review.lock.yml.

Related Items

Type	Link	Relevance
Issue	#369	Current triage target
File	.github/workflows/gh-aw-pr-review.md:116	Source prompt already instructs linked-issue lookup
File	.github/workflows/gh-aw-pr-review.lock.yml:539	Compiled workflow includes same behavior
File	.github/workflows/gh-aw-docs-pr-review.md:129	Parallel docs review workflow has equivalent instruction
PR	#205	Added docs PR review workflow, including linked-issue context mention
PR	#142	Prompt-guidance expansion effort (contextual related history)

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.