Skip to content

Commit 1cb2548

Browse files
dcarleyclaude
andcommitted
ci(claude-review): Use tracking comment summary
Review runs can end without posting anything to the PR, leaving no visible record that the review happened (upstream issue anthropics/claude-code-action#1087, still open with no input-level fix). Enable `track_progress: true` so the action forces tag mode and maintains a tracking comment on the PR: the comment is created before the model runs and is finalized with the outcome and a job link even if the model fails to follow the prompt, a stronger guarantee than a prompt-driven `gh pr comment` instruction. Tag mode's default prompt already directs the model to write its review into the tracking comment, so instructing it to post a separate summary comment would duplicate the same content (the tracking comment carrying a full review is observable in the wild, e.g. aws/secrets-store-csi-driver-provider-aws#629 runs this same pattern). Keep only the content requirement in the prompt: when there are no issues, the summary must state specifically what was reviewed and verified rather than a bare "no issues found" — the false sense of security that motivated switching review methodologies. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent a1a1e35 commit 1cb2548

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

.github/workflows/claude-review.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ jobs:
4343
--dangerously-skip-permissions
4444
--allowedTools "mcp__github_inline_comment__*"
4545
plugins: 'superpowers@claude-plugins-official'
46+
track_progress: true
4647
prompt: |
4748
Review PR #${{ github.event.pull_request.number }} in ${{ github.repository }}.
4849
@@ -57,3 +58,6 @@ jobs:
5758
- Post each issue as an inline comment on the relevant line using
5859
the mcp__github_inline_comment__create_inline_comment tool, so
5960
findings are threaded and individually addressable.
61+
- Finish by writing the review summary into the tracking comment.
62+
If there are no issues, say specifically what you reviewed and
63+
verified rather than a bare "no issues found".

0 commit comments

Comments
 (0)