Code Review and GitHub Actions

Code Review is a managed Claude service that reads a pull request against the whole codebase and posts its findings as inline comments.

Last updated: 28 Sep, 2026 · Claude Code

Work that ran unattended most needs a second reader. There are two ways to get one, and they are not the same product.

Code Review reads the change in the context of the whole codebase rather than the diff alone, which is the part a human reviewer usually skips. Findings do not approve or block the pull request, so it slots in beside whatever review process already exists.

You steer what it flags with a CLAUDE.md or a REVIEW.md in the repository. That is the same file from the CLAUDE.md lesson doing a second job: the conventions you wrote for the session are the conventions the review holds you to.

The action, in one file

name: Claude
on:
  issue_comment:
    types: [created]

jobs:
  claude:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
      issues: write
      id-token: write
      actions: read
    steps:
      - uses: actions/checkout@v6
      - uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

With that in place, mentioning @claude in a pull request or an issue starts a run in your own CI, with your repository checked out. It is the headless mode from the last lesson with GitHub events as the trigger.

The action reads the key from a repository secret. In GitHub open Settings, then Secrets and variables, then Actions, choose New repository secret, name it ANTHROPIC_API_KEY and paste a Console key. To use your plan instead, save the token from claude setup-token as a secret named CLAUDE_CODE_OAUTH_TOKEN and pass it as claude_code_oauth_token in place of anthropic_api_key. Running /install-github-app inside Claude Code sets this up for you.

Related

• Previous: Headless mode and JSON output
• Next: MCP
• Reference: Claude Code docs