Repository navigation
SST-259 Add Claude code review workflow for pull requests - #1581
Merged
Merged
Conversation
Reviews each PR on open and on every push (only new commits), posts inline comments plus one summary comment that is updated in place, and loads the Jira ticket from the branch name (CS-/SST-) as context. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yuryyas
marked this pull request as ready for review
November 17, 2026 13:18
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.
Summary
New workflow
.github/workflows/claude-review.ymlruns Claude Code on every PR to review it and post comments.claude-opus-5-5, max 40 turns, 20 min timeout. A new push cancels the run still in progress, and the next run picks up its commits.git/gh, file reads, inline comments and the PR summary comment. Claude can't edit, push, approve or merge.Setup required before marking ready (admin)
No keys are stored in the repo. The workflow reads them from repository secrets (Settings → Secrets and variables → Actions):
ANTHROPIC_API_KEY<Anthropic API key from the org Claude Console; separate workspace with a monthly spend limit>JIRA_USERNAME<email of a read-only Jira service account>JIRA_API_TOKEN<API token for that account, created at id.atlassian.com → Security → API tokens>claude[bot]through it.Evidence
Checked locally:
CS-447_Reports_reappearing_after_removal→CS-447,SST-5-Validate-...→SST-5, and nothing foremails_validation_fix,dependabot/...,OS-123-x.gh pr commentsupports--edit-last --create-if-none.Not tested yet (needs the secrets and the App):
${JIRA_*}expansion inside--mcp-config.--edit-lastedits the bot's own summary comment.mcp__jira__jira_get_issue.This PR is a draft, so the workflow skips it. Once setup is done, mark it ready for review: it then reviews itself, which is the first real test.
Merge Danger
Door: two-way. Delete the file or disable the workflow to turn it off.
Blast Radius: PR comments.
🤖 Generated with Claude Code