Skip to content

chore(deps): update azure azure-sdk-for-net monorepo #1337

chore(deps): update azure azure-sdk-for-net monorepo

chore(deps): update azure azure-sdk-for-net monorepo #1337

name: Claude Code Review
on:
pull_request:
types: [opened, synchronize, ready_for_review, reopened]
# Optional: Only run on specific file changes
# paths:
# - "src/**/*.ts"
# - "src/**/*.tsx"
# - "src/**/*.js"
# - "src/**/*.jsx"
workflow_dispatch:
inputs:
pr_number:
description: 'Pull request number to review'
required: true
type: number
jobs:
claude-review:
# Optional: Filter by PR author
# if: |
# github.event.pull_request.user.login == 'external-contributor' ||
# github.event.pull_request.user.login == 'new-developer' ||
# github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
runs-on: ubuntu-latest
permissions:
contents: write # Allows pushing fixes/commits
pull-requests: write # Allows posting review comments
issues: write # Allows creating/updating issues
checks: write # Allows creating check runs
statuses: write # Allows updating commit statuses
id-token: write # Required for OIDC authentication
steps:
- name: Checkout repository
uses: actions/checkout@v6
with:
fetch-depth: 1
- name: Run Claude Code Review
id: claude-review
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'
plugins: 'code-review@claude-code-plugins'
prompt: |
Instructions:
- ALWAYS post a review comment, even if no issues are found. If the code is good, acknowledge it.
- Compare the current state of the PR against any previous PR comments to make sure they have been addressed.
- You MUST post your review as a PR comment using `gh pr review` or `gh pr comment` before finishing. Do not just output the review - actually post it to the PR.
- When you find issues, ALWAYS suggest better approaches or architectural improvements, not just minor optimizations.
- Focus on:
* Design patterns that could be improved
* Alternative approaches that are more maintainable or scalable
* Architectural concerns or anti-patterns
* Better abstractions or simplifications
- Skip minor style/formatting issues unless they impact readability significantly.
- Always explain WHY the suggested approach is better, not just WHAT to change.
Use the code review skill to run this review: /code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number || inputs.pr_number }}
claude_args: "--allowedTools Bash,Read,Glob,Grep,WebFetch,WebSearch"
# See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
# or https://code.claude.com/docs/en/cli-reference for available options