[CDX-265] Add CC workflow

[Alexey-Pavlov]

No description provided.

[Copilot]

Pull request overview

This PR adds a GitHub Actions workflow to enable automated Claude AI code reviews on pull requests. The workflow integrates a reusable workflow from the Constructor-io organization's shared resources repository, following the existing pattern used for other organizational workflows in this repository.

Key Changes

• Adds a new workflow file that triggers Claude PR reviews on pull request events (opened, ready_for_review, synchronize)
• Uses the Constructor-io reusable workflow pattern with secrets: inherit for configuration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[constructor-claude-bedrock]

Code Review Summary

This PR adds a GitHub Actions workflow to enable automated Claude code reviews on pull requests. The workflow is clean, simple, and follows a reusable workflow pattern by referencing a shared workflow from Constructor-io/shared-claude-code-resources-public. The implementation is straightforward and adds value by automating code review processes.

Detailed Feedback

Positive Aspects

• [General] The workflow follows GitHub Actions best practices by using a reusable workflow pattern, promoting consistency across Constructor.io repositories
• [File: .github/workflows/claude-review.yml Line: L3-L5] Appropriate trigger events (opened, ready_for_review, synchronize) ensure reviews happen at the right times without being excessive
• [General] Using secrets: inherit is appropriate for a reusable workflow that needs access to repository secrets
• [General] The workflow naming is clear and descriptive

Considerations & Suggestions

1. [File: .github/workflows/claude-review.yml Line: L9] Consider pinning the workflow reference to a specific commit SHA instead of @main for better security and stability:

uses: Constructor-io/shared-claude-code-resources-public/.github/workflows/claude-code-review.yml@<commit-sha>

This prevents unexpected changes if the shared workflow is modified. However, if @main is intentional for receiving updates automatically, this is acceptable—just ensure the shared workflow repository has proper change management.

2. [General - Documentation] Consider adding a brief comment at the top of the workflow file explaining its purpose and linking to documentation about Claude code reviews, especially if this is new to the team:

# Automatically runs Claude AI code reviews on pull requests
# See: <link-to-internal-docs-if-available>
name: Claude PR Review

3. [General - Permissions] The workflow uses secrets: inherit, which is necessary for the reusable workflow. However, it might be worth verifying that the called workflow has appropriate permission scopes defined (especially pull-requests: write if it needs to comment). This is more of a note for the shared workflow maintainers.

4. [General - Draft PRs] The current triggers include ready_for_review which is great, but consider whether you want to exclude draft PRs from initial reviews to save resources:

on:
  pull_request:
    types: [opened, ready_for_review, synchronize]
    # Optionally add this condition to the job level:
    # if: github.event.pull_request.draft == false

This depends on team preference—some teams want reviews on drafts, others don't.

5. [General - Consistency] The CodeQL workflow uses branches: [ master ] to limit when it runs. Consider whether the Claude review should also be limited to specific branches, or if running on all PRs (current behavior) is desired. The current approach is fine for most use cases.

Conclusion

This is a well-implemented, straightforward workflow addition. The code is clean and follows GitHub Actions best practices. The suggestions above are minor improvements around security hardening (SHA pinning) and team convenience (documentation, draft PR handling), but none are blocking issues.

Recommendation: Approve ✅

The workflow is ready to merge as-is. The optional improvements can be addressed in follow-up PRs if desired.