Set Up Claude Code GitHub Actions with /install-github-app
You don't need to manually configure workflow files, install GitHub apps, or wire up secrets to get Claude responding to @claude mentions in your PRs. There's a one-command setup.
claude
> /install-github-app
This walks you through installing the Claude GitHub app, adding your ANTHROPIC_API_KEY as a repository secret, and copying the workflow file into .github/workflows/. Once done, tag @claude in any issue or PR comment and it will analyse context and respond.
If you want to customise the behaviour, pass CLI arguments through the claude_args parameter in your workflow file:
- uses: anthropics/claude-code-action@v1
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
claude_args: "--max-turns 5 --model claude-sonnet-4-6"
You can also set up automated workflows that trigger on schedules, PR opens, or any GitHub event by adding a prompt parameter instead of relying on @claude mentions.
You'll need to be a repository admin to install the app. The app requests read and write permissions for Contents, Issues, and Pull Requests.
One command to turn every PR into a conversation with Claude.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.