[CDX-265] Add CC workflow

[Alexey-Pavlov]

No description provided.

[Copilot]

Pull request overview

This PR adds a Claude Code Review workflow to automate code review on pull requests. It introduces a GitHub Actions workflow that integrates with Constructor.io's shared Claude code review resources and includes comprehensive review guidelines documentation.

• Adds GitHub Actions workflow to trigger Claude PR reviews automatically
• Provides detailed code review command documentation with security, performance, and testing standards

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/claude-review.yml	Configures GitHub Actions workflow to run Claude PR reviews on opened, ready_for_review, and synchronize events
.claude/commands/review.md	Comprehensive documentation defining review standards, coding guidelines, and output format for Claude code reviews

---

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

[Copilot]

The first line of the workflow file appears to have leading whitespace before name:. YAML files should not have leading whitespace on the first line. Remove the leading spaces.

[constructor-claude-bedrock]

Code Review Results

✅ Strengths

This PR adds a well-structured Claude Code review workflow and comprehensive review guidelines.

🚨 Critical Issues

None

⚠️ Important Issues

• [File: .github/workflows/claude-review.yml Line: 9] Missing concurrency configuration. Other workflows in this repository (lint.yml, run-tests.yml) use concurrency settings to cancel in-progress runs when new commits are pushed. Add:

concurrency:
  group: claude-review-${{ github.head_ref }}
  cancel-in-progress: true

This prevents multiple review jobs from running simultaneously on the same PR, saving CI resources and providing clearer feedback.

• [File: .claude/commands/review.md Line: 113] The testing requirement states "All code changes must be covered by tests unless explicitly discussed with team", but this meta-PR adding workflow configuration has no tests. While tests for GitHub Actions workflows are uncommon, consider documenting in the review guidelines whether workflow/configuration changes require validation or are exempt from test coverage requirements.

💡 Suggestions

• [File: .github/workflows/claude-review.yml Line: 9] Consider adding permissions configuration to follow the principle of least privilege, especially if the reusable workflow needs to comment on PRs. Example:

jobs:
  review:
    permissions:
      pull-requests: write
      contents: read
    uses: Constructor-io/shared-claude-code-resources-public/.github/workflows/claude-code-review.yml@main
    secrets: inherit

• [File: .claude/commands/review.md Line: 72] The guideline mentions "package-lock.json changes: correspond to package.json changes" but this is a Node.js-specific check. Since this appears to be a generic review template that could be reused across different project types, consider clarifying that language/ecosystem-specific checks apply only to relevant projects.

• [File: .claude/commands/review.md Line: 14] The process references origin/master but the PR view shows this repository might use main as the default branch. Consider updating line 14 to say "origin/main (or origin/master)" for clarity, or dynamically detect the default branch.

Overall Assessment: ⚠️ Needs Work

The workflow setup is solid, but adding concurrency controls (which all other workflows in this repo use) is important for consistency and resource management.