Claude Code GitHub Actions Setup Guide (2026)

The Problem

You want Claude Code to automatically respond to GitHub issues, review pull requests, and implement features directly in your CI/CD pipeline, but you do not know how to set up the integration.

Quick Fix

The fastest setup uses Claude Code’s built-in installer. Open Claude Code and run:

/install-github-app

This guides you through installing the GitHub app and configuring repository secrets.

What’s Happening

Claude Code GitHub Actions brings AI-powered automation to your GitHub workflow. When you mention @claude in any PR or issue comment, Claude analyzes your code, creates pull requests, implements features, and fixes bugs while following your project’s CLAUDE.md standards.

The action is built on the Claude Agent SDK and runs on GitHub’s runners, so your code stays within GitHub’s infrastructure. It supports two modes: interactive mode (responds to @claude mentions) and automation mode (runs immediately with a prompt).

Step-by-Step Fix

Step 1: Install the GitHub app

You need repository admin access. Install the Claude GitHub app:

Visit github.com/apps/claude and install it to your repository.

The app requires these permissions:

  • Contents: Read & write (to modify repository files)
  • Issues: Read & write (to respond to issues)
  • Pull requests: Read & write (to create PRs and push changes)

Step 2: Add your API key

Add ANTHROPIC_API_KEY to your repository secrets:

  1. Go to your repository Settings
  2. Navigate to Secrets and Variables > Actions
  3. Click “New repository secret”
  4. Name: ANTHROPIC_API_KEY
  5. Value: your Anthropic API key

Step 3: Create the workflow file

Create .github/workflows/claude.yml:

name: Claude Code
on:
 issue_comment:
 types: [created]
 pull_request_review_comment:
 types: [created]
 issues:
 types: [opened]
jobs:
 claude:
 if: contains(github.event.comment.body, '@claude') || contains(github.event.issue.body, '@claude')
 runs-on: ubuntu-latest
 permissions:
 contents: write
 pull-requests: write
 issues: write
 steps:
 - uses: anthropics/claude-code-action@v1
 with:
 anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

Step 4: Customize with claude_args

Pass additional configuration to Claude Code:

- uses: anthropics/claude-code-action@v1
 with:
 anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
 claude_args: |
 --append-system-prompt "Follow our coding standards"
 --max-turns 10
 --model claude-sonnet-4-6

Step 5: Create automation workflows

For tasks that run automatically (not triggered by @claude mentions), use the prompt input:

name: Auto Review
on:
 pull_request:
 types: [opened, synchronize]
jobs:
 review:
 runs-on: ubuntu-latest
 permissions:
 contents: read
 pull-requests: write
 steps:
 - uses: anthropics/claude-code-action@v1
 with:
 prompt: "Review this PR for security issues and code quality"
 anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

Step 6: Use with Bedrock or Vertex AI

For AWS Bedrock:

- uses: anthropics/claude-code-action@v1
 with:
 claude_args: --model bedrock:us.anthropic.claude-sonnet-4-6-20250514-v1:0
 env:
 AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
 AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
 AWS_REGION: us-east-1

Step 7: Test the integration

Create a test issue or PR comment with @claude followed by a task description:

@claude Review this PR for potential security issues and suggest improvements

Claude will respond with its analysis directly in the GitHub conversation.

Migrating from beta

If you are upgrading from the beta version:

Old Beta Input New v1.0 Input
mode Removed (auto-detected)
direct_prompt prompt
custom_instructions claude_args: --append-system-prompt
max_turns claude_args: --max-turns
model claude_args: --model

Prevention

Add a CLAUDE.md file to your repository with project-specific instructions. Claude Code GitHub Actions reads this file automatically, ensuring consistent behavior across all automated tasks.

Set reasonable --max-turns limits to control API costs per workflow run. Start with 10 turns and adjust based on your needs.

Level Up Your Claude Code Workflow

The developers who get the most out of Claude Code aren’t just fixing errors — they’re running multi-agent pipelines, using battle-tested CLAUDE.md templates, and shipping with production-grade operating principles.

**Written by Michael** — solo dev, Da Nang, Vietnam. 50K+ Chrome extension users. $500K+ on Upwork (100% Job Success). Runs 5 Claude Max subs in parallel. Built this site with autonomous agent fleets. [See what I'm building →](https://zovo.one)
**Without a CLAUDE.md — what actually happens:** You type: "Add auth to my Next.js app" Claude generates: `pages/api/auth/[...nextauth].js` — wrong directory (you're on App Router), wrong file extension (you use TypeScript), wrong NextAuth version (v4 patterns, you need v5), session handling that doesn't match your middleware setup. You spend 40 minutes reverting and rewriting. Claude was "helpful." **With the Zovo Lifetime CLAUDE.md:** Same prompt. Claude reads 300 lines of context about YOUR project. Generates: `app/api/auth/[...nextauth]/route.ts` with v5 patterns, your session types, your middleware config, your test patterns. Works on first run. You commit and move on. That's the difference a $99 file makes. **[Get the CLAUDE.md for your stack →](https://zovo.one/lifetime?utm_source=ccg&utm_medium=cta-beforeafter&utm_campaign=claude-code-github-actions-setup-guide)**
This took me 3 hours to figure out. I put it in a CLAUDE.md so I'd never figure it out again. Now Claude gets it right on the first try, every project. 16 framework templates. Next.js, FastAPI, Laravel, Rails, Go, Rust, Terraform, and 9 more. Each one 300+ lines of "here's exactly how this stack works." Copy into your project. Done. **[See the templates →](https://zovo.one/lifetime?utm_source=ccg&utm_medium=cta-deploy&utm_campaign=claude-code-github-actions-setup-guide)** $99 once. Yours forever. I keep adding templates monthly.

Try it: Paste your error into our Error Diagnostic for an instant fix.

See Also