Add Claude Code GitHub Workflow

[jonahgabriel]

🤖 Installing Claude Code GitHub App

This PR adds a GitHub Actions workflow that enables Claude Code integration in our repository.

What is Claude Code?

Claude Code is an AI coding agent that can help with:

• Bug fixes and improvements
• Documentation updates
• Implementing new features
• Code reviews and suggestions
• Writing tests
• And more!

How it works

Once this PR is merged, we'll be able to interact with Claude by mentioning @claude in a pull request or issue comment.
Once the workflow is triggered, Claude will analyze the comment and surrounding context, and execute on the request in a GitHub action.

Important Notes

• This workflow won't take effect until this PR is merged
• @claude mentions won't work until after the merge is complete
• The workflow runs automatically whenever Claude is mentioned in PR or issue comments
• Claude gets access to the entire PR or issue context including files, diffs, and previous comments

Security

• Our Anthropic API key is securely stored as a GitHub Actions secret
• Only users with write access to the repository can trigger the workflow
• All Claude runs are stored in the GitHub Actions run history
• Claude's default tools are limited to reading/writing files and interacting with our repo by creating comments, branches, and commits.
• We can add more allowed tools by adding them to the workflow file like:

allowed_tools: Bash(npm install),Bash(npm run build),Bash(npm run lint),Bash(npm run test)

There's more information in the Claude Code action repo.

After merging this PR, let's try mentioning @claude in a comment on any PR to get started!

[claude]

PR Review: Add Claude Code GitHub Workflow

Thank you for proposing the Claude Code integration! However, I've identified a critical issue with this PR.

🚨 Critical Issue

The PR is empty - it contains 0 additions, 0 deletions, and no files. The workflow file mentioned in the description (presumably .github/workflows/claude-code.yml) is not actually included in the PR.

Required Changes

To properly implement this feature, the PR needs to include:

1. GitHub Actions Workflow File (.github/workflows/claude-code.yml or similar):

   • Trigger on issue_comment and pull_request_review_comment events
   • Check for @claude mentions
   • Set up Anthropic API key from secrets
   • Configure allowed tools as described
   • Reference the claude-code-action

2. Example Workflow Structure:

   name: Claude Code
   on:
     issue_comment:
       types: [created]
     pull_request_review_comment:
       types: [created]
   
   jobs:
     claude-code:
       if: contains(github.event.comment.body, '@claude')
       runs-on: ubuntu-latest
       steps:
         - uses: anthropics/claude-code-action@v1
           with:
             anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
             allowed_tools: |
               Bash(npm install)
               Bash(npm run build)
               Bash(npm run lint)
               Bash(npm run test)

Security Considerations (for when files are added)

• ✅ Good: API key as GitHub secret
• ✅ Good: Write access requirement for triggering
• ✅ Good: Explicit allowed tools list
• ⚠️ Consider: Adding branch protection for main/master
• ⚠️ Consider: Limiting which events trigger the workflow
• ⚠️ Consider: Adding concurrency controls to prevent multiple simultaneous runs

Documentation Quality

The PR description is excellent:

• Clear explanation of what Claude Code is
• Good usage instructions
• Proper security documentation
• Important notes about when the workflow takes effect

Recommendations

1. Add the workflow file to this PR
2. Customize allowed_tools based on the OmniClaude project's actual build/test commands
3. Consider adding to CLAUDE.md a section about the GitHub Actions integration
4. Test the workflow in a fork before merging to ensure it works as expected
5. Set up the ANTHROPIC_API_KEY secret in repository settings before merging

Alignment with CLAUDE.md

Since OmniClaude is a toolkit for Claude Code enhancement, this integration is highly appropriate. Consider documenting:

• How Claude Code will interact with the provider switching system
• Whether Claude should respect the current provider configuration
• How to test Claude's suggestions across different providers

Status: ❌ Cannot approve - PR requires the actual workflow files to be added.

Please push the workflow file and I'll be happy to review the implementation details!