[deep-report] PR Code Quality Reviewer reads a per-PR cache-memory continuity file that is never written #52742

Description

.github/workflows/pr-code-quality-reviewer.md:99 instructs the agent: "If this PR has been reviewed before, also read /tmp/gh-aw/cache-memory/pr-${{ github.event.issue.number || github.event.pull_request.number }}.json before Step 2 to inform theme continuity; otherwise skip." A full read of the workflow file (191 lines) confirms there is no corresponding instruction anywhere to ever write that file - Step 4 ("Write Review Comments", line 135) only posts the review comment, it never persists a per-PR memory snapshot. The read is effectively always a no-op/skip.

Expected Impact

Either add a step that writes a small per-PR summary to that cache-memory path after each review (enabling the intended theme-continuity behavior across repeat reviews of the same PR), or remove the dead read instruction if continuity isn't actually wanted. Currently the workflow silently does neither, which is misleading to anyone reading the prompt.

Suggested Agent

Any agentic-workflow-prompt-maintenance agent, or a direct edit to .github/workflows/pr-code-quality-reviewer.md.

Estimated Effort

Quick (< 1 hour).

Data Source

DeepReport Intelligence Briefing analysis run 2026-08-14, surfaced by discussion #52561 (cache-strategy), source-verified directly against .github/workflows/pr-code-quality-reviewer.md.

Generated by 🔬 Deep Report · agent · 279.4 AIC · ⌖ 53.2 AIC · ⊞ 11.4K · ◷

• expires on Aug 16, 2026, 7:14 AM UTC-08:00