Add Claude review workflow#5258
Merged
Merged
Conversation
Member
Author
|
Closing because this workflow won't work for this repo because all contributions are from forks, and some thoughtful approach to only running on forks from members will be needed. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Actions workflow to automatically run an Anthropic Claude-based PR review on key pull request events, aiming to provide additional review perspectives alongside existing CI.
Changes:
- Introduces
.github/workflows/claude-review.ymltriggered on PR open/sync/reopen/ready-for-review events. - Configures per-PR concurrency cancellation to avoid overlapping runs.
- Runs
anthropics/claude-code-actionwith a basic review prompt and inline-comment tooling.
anupsdf
reviewed
May 7, 2026
anupsdf
previously approved these changes
May 7, 2026
kanwalpreetd
reviewed
May 8, 2026
kanwalpreetd
reviewed
May 8, 2026
kanwalpreetd
reviewed
May 8, 2026
Member
Author
|
@kanwalpreetd Thanks for the solid review. I've addressed your feedback. |
leighmcculloch
force-pushed
the
add-claude-review-workflow
branch
from
cd33d72 to
36a4291
Compare
This was referenced May 8, 2026
kanwalpreetd
approved these changes
May 8, 2026
anupsdf
approved these changes
May 8, 2026
marwen-abid
pushed a commit
to stellar/stellar-disbursement-platform-backend
that referenced
this pull request
May 27, 2026
### What
Apply a best practice to the `automated_release_process` workflow:
- Move the broad `contents: write`/`pull-requests: write`/`issues:
write`/`id-token: write` scope from workflow level to the single job
that needs it; set top-level `permissions: {}` so any future job added
to this file inherits nothing by default.
### Why
This is pretty minor, but brings this workflow in line with the
Claude-action security standards being applied across the stellar org
(see `stellar/stellar-core` [PR
#5258](stellar/stellar-core#5258) and the
[claude-code-action security
guide](https://github.com/anthropics/claude-code-action/blob/main/docs/security.md)).
Without `permissions: {}` at the workflow root, any future job added to
this file would silently inherit the broad write scopes. Moving them to
the job level limits the blast radius if this workflow expands in the
future.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add Claude review workflow.
To get a larger variety of review perspectives on changes.
The prompt in the workflow is super basic as a starting point. I'm curious to see how it fares initially without too much specialisation. I expect with the skills in this repo a better prompt is possible, but I'd start with this, and potentially run a separate prompt to compare before eagerly specialising.
Checklist
clang-formatv8.0.0 (viamake formator the Visual Studio extension)