@manufac/sculptor 1.0.0

package/.github/workflows/feedback.yml

@@ -0,0 +1,50 @@
+name: Claude Feedback Collector
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  collect-feedback:
+    if: >
+      github.event.issue.pull_request != null &&
+      contains(github.event.comment.body, '@claude-feedback')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create feedback issue with diff permalink
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          REPO="${{ github.repository }}"
+          PR_NUMBER="${{ github.event.issue.number }}"
+
+          PR_JSON=$(gh pr view "$PR_NUMBER" --repo "$REPO" --json headRefOid)
+          COMMIT_SHA=$(echo "$PR_JSON" | jq -r '.headRefOid')
+
+          DIFF_URL="https://github.com/${REPO}/pull/${PR_NUMBER}/files?diff=unified&sha=${COMMIT_SHA}" 
+          FEEDBACK_REPO="manufac-analytics/sculptor"
+
+          gh issue create \
+            --repo "$FEEDBACK_REPO" \
+            --title "Claude feedback - PR #${PR_NUMBER}" \
+            --body "$(cat <<EOF
+                    ## Trigger
+                    @claude-feedback mentioned in PR comment.
+
+                    ## PR Context
+                    - Repository: ${REPO}
+                    - PR: #${PR_NUMBER}
+                    - Commit SHA: ${COMMIT_SHA}
+
+                    ## Diff (Permalink)
+                    ${DIFF_URL}
+
+                    ## Comment
+                    Author: @${{ github.event.comment.user.login }}
+                    URL: ${{ github.event.comment.html_url }}
+
+                    \`\`\`
+                    ${{ github.event.comment.body }}
+                    \`\`\`
+                    EOF
+                    )"

package/.github/workflows/inline.yml

@@ -0,0 +1,119 @@
+name: Software Engineer Code Review
+
+on:
+  pull_request:
+    types: [opened] # Trigger when a PR is created
+  issue_comment:
+    types: [created] # Trigger when a comment is created
+
+jobs:
+  claude-review:
+    if: |
+      (github.event_name == 'pull_request') ||
+      (github.event_name == 'issue_comment' && github.event.issue.pull_request && contains(github.event.comment.body, '@claude-inline'))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+      issues: read
+      id-token: write
+
+    steps:
+      - name: Set PR number and ref
+        id: pr-info
+        run: |
+          if [ "${{ github.event_name }}" == "pull_request" ]; then
+            echo "pr_number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/${{ github.event.pull_request.number }}/merge" >> $GITHUB_OUTPUT
+            echo "commit_sha=${{ github.event.pull_request.head.sha }}" >> $GITHUB_OUTPUT
+          else
+            PR_NUM=${{ github.event.issue.number }}
+            echo "pr_number=$PR_NUM" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/$PR_NUM/merge" >> $GITHUB_OUTPUT
+            # Use gh api instead of gh pr view to avoid git dependency
+            COMMIT_SHA=$(gh api repos/${{ github.repository }}/pulls/$PR_NUM --jq '.head.sha')
+            echo "commit_sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Checkout PR code
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ steps.pr-info.outputs.pr_ref }}
+          fetch-depth: 0
+
+      - name: Run Claude Code Review for functional issues
+        id: claude-review-functional
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          prompt: |
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            Provide inline code review comments only on lines modified in the PR diff. Do not create comments on lines that are not modified.
+
+            Review Process:
+            1. Use `gh pr diff ${{ steps.pr-info.outputs.pr_number }}` to analyze all changes in the PR
+            2. For each issue you find (bugs, performance issues, security issues), collect them to create inline comments
+
+            To create inline comments, use `mcp__github_inline_comment__create_inline_comment` tool. :
+
+            Guidelines:
+            - Focus on actionable feedback: bugs, performance, security
+            - Be concise and direct
+            - Create inline comments for specific code issues
+            - Do not provide appreciation comments like "Good use of the const + type pattern per CLAUDE.md Form Utils Typings section. The as const combined with type extraction provides both literal inference and type safety. Consider adding satisfies Record<string, number> for additional compile-time validation: export const RecognitionStatus = { ... } as const satisfies Record<string, number>;"
+            - Review comment should provide a direct solution or guide the implementor in direction of the solution rather than open ended questions.
+
+          claude_args: |
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*)"
+            --model claude-haiku-4-5-20251001
+            --system-prompt "As a software engineer with complete knowledge of the codebase, you are reviewing a pull request."
+
+      - name: Run Claude Code Review for semantic and convention analysis
+        id: claude-review-semantic
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          prompt: |
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            Provide inline code review comments only on lines modified in the PR diff. Do not create comments on lines that are not modified.
+
+            Review Process:
+            1. Use `gh pr diff ${{ steps.pr-info.outputs.pr_number }}` to analyze all changes in the PR
+            2. Follow the repository's CLAUDE.md: 
+              - `Variable naming guidelines` section for variable naming conventions.
+              - `Types naming conventions` section for type naming conventions.
+              - `File naming conventions` section for file naming conventions.
+              - `Coding conventions guidelines` section for coding conventions.
+
+            3. Do not deviate from the guidelines in CLAUDE.md.
+
+            To create inline comments, use `mcp__github_inline_comment__create_inline_comment` tool.
+
+            Source of Truth and Decision Rules:
+            - The guidelines in CLAUDE.md are the highest priority and always authoritative for naming and coding conventions.
+            - Existing codebase patterns must not override the guidelines.
+            - If a pattern in the PR violates the guidelines, suggest correcting the code, even if the same pattern exists elsewhere in the codebase.
+            - If a pattern in the PR does NOT violate the guidelines and is repeatedly used in multiple places in the existing codebase but is not documented in CLAUDE.md, create an inline comment stating that the guideline is missing or incomplete.
+            - Do not suggest changing or relaxing the guidelines based on existing code.
+            - Do not invent new rules beyond what is defined in CLAUDE.md.
+
+            Guidelines:
+            - Focus on actionable feedback related to naming conventions (violations or guideline gaps).
+            - Be concise and direct
+            - Create inline comments for specific code issues
+            - Review comment should provide appropriate naming suggestions.
+
+          claude_args: |
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*)"
+            --model claude-haiku-4-5-20251001
+            --system-prompt "As a software engineer with complete knowledge of the codebase, you are reviewing a pull request."

package/.github/workflows/insights.yml

@@ -0,0 +1,160 @@
+name: Senior Software Engineer Code Review
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  claude:
+    if: |
+      github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude') && !contains(github.event.comment.body, '@claude-inline') && (github.event.comment.user.login == 'manufac-nmohan' || github.event.comment.user.login == 'manufac-nrawat')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Set PR/Issue number and ref
+        id: pr-info
+        run: |
+          ISSUE_NUM=${{ github.event.issue.number }}
+          echo "issue_number=$ISSUE_NUM" >> $GITHUB_OUTPUT
+
+          # Check if this is a PR comment by checking if pull_request field exists
+          HAS_PR_FIELD=$(gh api repos/${{ github.repository }}/issues/$ISSUE_NUM --jq '.pull_request != null')
+
+          if [ "$HAS_PR_FIELD" == "true" ]; then
+            PR_NUM=$ISSUE_NUM
+            echo "pr_number=$PR_NUM" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/$PR_NUM/merge" >> $GITHUB_OUTPUT
+            COMMIT_SHA=$(gh api repos/${{ github.repository }}/pulls/$PR_NUM --jq '.head.sha')
+            echo "commit_sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
+            echo "is_pr=true" >> $GITHUB_OUTPUT
+          else
+            echo "is_pr=false" >> $GITHUB_OUTPUT
+            echo "pr_ref=${{ github.ref }}" >> $GITHUB_OUTPUT
+            echo "commit_sha=${{ github.sha }}" >> $GITHUB_OUTPUT
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          ref: ${{ steps.pr-info.outputs.pr_ref }}
+          fetch-depth: 0
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          claude_args: |
+            --model claude-sonnet-4-5-20250929
+            --allowed-tools "Bash(gh api:*),Write"
+            --system-prompt "As a senior software engineer with complete knowledge of the codebase and project requirements, you are reviewing a pull request."
+          prompt: |
+            REPO: ${{ github.repository }}
+            ISSUE NUMBER: ${{ steps.pr-info.outputs.issue_number }}
+            IS PR: ${{ steps.pr-info.outputs.is_pr }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            ## STEP 1: GATHER CONTEXT
+
+            1. Fetch PR files and diff:
+              `gh api /repos/${{ github.repository }}/pulls/${{ steps.pr-info.outputs.pr_number }}/files`
+
+            2. Retrieve existing comments to avoid duplication:
+              `gh api /repos/${{ github.repository }}/issues/${{ steps.pr-info.outputs.issue_number }}/comments`
+
+            3. Get PR description and metadata:
+              `gh api /repos/${{ github.repository }}/pulls/${{ steps.pr-info.outputs.pr_number }}`
+
+            ## STEP 2: DEEP ANALYSIS
+
+            Analyze the changes focusing on:
+
+            **Architecture & Design:**
+            - Does this change align with existing architectural patterns?
+            - Are there any design anti-patterns or code smells?
+            - Could this be implemented more elegantly or maintainably?
+
+            **Integration Impact:**
+            - How do these changes affect existing modules and their contracts?
+            - Are there potential breaking changes or backward compatibility issues?
+            - What are the ripple effects on dependent code?
+
+            **Performance & Scalability:**
+            - Are there performance bottlenecks (O(n²) algorithms, N+1 queries, etc.)?
+            - How will this behave under load or with large datasets?
+            - Are there memory leak risks or resource management issues?
+
+            **Security & Reliability:**
+            - Are there security vulnerabilities (injection, XSS, authentication issues)?
+            - Is error handling robust and comprehensive?
+            - Are edge cases and failure scenarios handled?
+
+            **Code Quality:**
+            - Is the code testable? Are tests adequate?
+            - Is naming clear and consistent with the codebase?
+            - Are there opportunities for code reuse or consolidation?
+
+            ## STEP 3: VERIFY PREVIOUS FEEDBACK
+
+            - Check if existing review comments have been addressed
+            - Verify that suggested changes were implemented correctly
+            - Confirm that discussions have been resolved appropriately
+
+            ## STEP 4: POST REVIEW COMMENT
+
+            Format your review as a structured comment and post it:
+            ```
+              gh api POST /repos/${{ github.repository }}/issues/${{ steps.pr-info.outputs.issue_number }}/comments -f body="[Your formatted review]"
+            ```
+
+            ## COMMENT FORMATTING GUIDELINES
+
+            **Structure your comment as:**
+
+            ### 🎯 Summary
+            [2-3 sentence overview of the changes and overall assessment]
+
+            ### ✅ Strengths
+            [Highlight what was done well - be specific]
+
+            ### ⚠️ Critical Issues
+            [Issues that must be fixed before merge - include specific solutions]
+
+            ### 💡 Suggestions
+            [Optional improvements with code examples where helpful]
+
+            ### 📊 Impact Assessment
+            - **Functionality**: [How this affects existing features]
+            - **Performance**: [Expected performance impact]
+            - **Maintainability**: [Long-term maintenance considerations]
+
+            **Writing Style:**
+            - Be specific: Reference exact files, line numbers, and function names
+            - Be prescriptive: Provide concrete solutions, not just questions
+            - Be concise: Every sentence should add value
+            - Be constructive: Frame feedback as opportunities for improvement
+            - Use code snippets to illustrate better approaches
+
+            **Prioritization:**
+            - Focus on high-impact issues first
+            - Don't nitpick trivial style issues if there are bigger concerns
+            - Group related feedback together
+
+            ## IMPORTANT CONSTRAINTS
+
+            - You MUST post your review as a GitHub comment, not just a job summary
+            - If no significant issues found, still provide a brief positive review
+            - Don't duplicate feedback already given in existing comments
+            - Tailor depth of review to the size/complexity of the PR
+            - For large PRs, focus on architectural concerns over line-by-line details
+
+            Begin your review now by fetching the necessary information.

package/.husky/pre-commit

@@ -0,0 +1,2 @@
+yarn pretty
+yarn lint

package/.prettierrc.mjs

@@ -0,0 +1,2 @@
+import config from "@manufac/prettier-config";
+export default config;

package/Readme.md

@@ -0,0 +1 @@
+# sculptor

package/dist/claude/feedback.yml

@@ -0,0 +1,50 @@
+name: Claude Feedback Collector
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  collect-feedback:
+    if: >
+      github.event.issue.pull_request != null &&
+      contains(github.event.comment.body, '@claude-feedback')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create feedback issue with diff permalink
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          REPO="${{ github.repository }}"
+          PR_NUMBER="${{ github.event.issue.number }}"
+
+          PR_JSON=$(gh pr view "$PR_NUMBER" --repo "$REPO" --json headRefOid)
+          COMMIT_SHA=$(echo "$PR_JSON" | jq -r '.headRefOid')
+
+          DIFF_URL="https://github.com/${REPO}/pull/${PR_NUMBER}/files?diff=unified&sha=${COMMIT_SHA}" 
+          FEEDBACK_REPO="manufac-analytics/sculptor"
+
+          gh issue create \
+            --repo "$FEEDBACK_REPO" \
+            --title "Claude feedback - PR #${PR_NUMBER}" \
+            --body "$(cat <<EOF
+                    ## Trigger
+                    @claude-feedback mentioned in PR comment.
+
+                    ## PR Context
+                    - Repository: ${REPO}
+                    - PR: #${PR_NUMBER}
+                    - Commit SHA: ${COMMIT_SHA}
+
+                    ## Diff (Permalink)
+                    ${DIFF_URL}
+
+                    ## Comment
+                    Author: @${{ github.event.comment.user.login }}
+                    URL: ${{ github.event.comment.html_url }}
+
+                    \`\`\`
+                    ${{ github.event.comment.body }}
+                    \`\`\`
+                    EOF
+                    )"

package/dist/claude/inline.yml

@@ -0,0 +1,119 @@
+name: Software Engineer Code Review
+
+on:
+  pull_request:
+    types: [opened] # Trigger when a PR is created
+  issue_comment:
+    types: [created] # Trigger when a comment is created
+
+jobs:
+  claude-review:
+    if: |
+      (github.event_name == 'pull_request') ||
+      (github.event_name == 'issue_comment' && github.event.issue.pull_request && contains(github.event.comment.body, '@claude-inline'))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+      issues: read
+      id-token: write
+
+    steps:
+      - name: Set PR number and ref
+        id: pr-info
+        run: |
+          if [ "${{ github.event_name }}" == "pull_request" ]; then
+            echo "pr_number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/${{ github.event.pull_request.number }}/merge" >> $GITHUB_OUTPUT
+            echo "commit_sha=${{ github.event.pull_request.head.sha }}" >> $GITHUB_OUTPUT
+          else
+            PR_NUM=${{ github.event.issue.number }}
+            echo "pr_number=$PR_NUM" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/$PR_NUM/merge" >> $GITHUB_OUTPUT
+            # Use gh api instead of gh pr view to avoid git dependency
+            COMMIT_SHA=$(gh api repos/${{ github.repository }}/pulls/$PR_NUM --jq '.head.sha')
+            echo "commit_sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Checkout PR code
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ steps.pr-info.outputs.pr_ref }}
+          fetch-depth: 0
+
+      - name: Run Claude Code Review for functional issues
+        id: claude-review-functional
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          prompt: |
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            Provide inline code review comments only on lines modified in the PR diff. Do not create comments on lines that are not modified.
+
+            Review Process:
+            1. Use `gh pr diff ${{ steps.pr-info.outputs.pr_number }}` to analyze all changes in the PR
+            2. For each issue you find (bugs, performance issues, security issues), collect them to create inline comments
+
+            To create inline comments, use `mcp__github_inline_comment__create_inline_comment` tool. :
+
+            Guidelines:
+            - Focus on actionable feedback: bugs, performance, security
+            - Be concise and direct
+            - Create inline comments for specific code issues
+            - Do not provide appreciation comments like "Good use of the const + type pattern per CLAUDE.md Form Utils Typings section. The as const combined with type extraction provides both literal inference and type safety. Consider adding satisfies Record<string, number> for additional compile-time validation: export const RecognitionStatus = { ... } as const satisfies Record<string, number>;"
+            - Review comment should provide a direct solution or guide the implementor in direction of the solution rather than open ended questions.
+
+          claude_args: |
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*)"
+            --model claude-haiku-4-5-20251001
+            --system-prompt "As a software engineer with complete knowledge of the codebase, you are reviewing a pull request."
+
+      - name: Run Claude Code Review for semantic and convention analysis
+        id: claude-review-semantic
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          prompt: |
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            Provide inline code review comments only on lines modified in the PR diff. Do not create comments on lines that are not modified.
+
+            Review Process:
+            1. Use `gh pr diff ${{ steps.pr-info.outputs.pr_number }}` to analyze all changes in the PR
+            2. Follow the repository's CLAUDE.md: 
+              - `Variable naming guidelines` section for variable naming conventions.
+              - `Types naming conventions` section for type naming conventions.
+              - `File naming conventions` section for file naming conventions.
+              - `Coding conventions guidelines` section for coding conventions.
+
+            3. Do not deviate from the guidelines in CLAUDE.md.
+
+            To create inline comments, use `mcp__github_inline_comment__create_inline_comment` tool.
+
+            Source of Truth and Decision Rules:
+            - The guidelines in CLAUDE.md are the highest priority and always authoritative for naming and coding conventions.
+            - Existing codebase patterns must not override the guidelines.
+            - If a pattern in the PR violates the guidelines, suggest correcting the code, even if the same pattern exists elsewhere in the codebase.
+            - If a pattern in the PR does NOT violate the guidelines and is repeatedly used in multiple places in the existing codebase but is not documented in CLAUDE.md, create an inline comment stating that the guideline is missing or incomplete.
+            - Do not suggest changing or relaxing the guidelines based on existing code.
+            - Do not invent new rules beyond what is defined in CLAUDE.md.
+
+            Guidelines:
+            - Focus on actionable feedback related to naming conventions (violations or guideline gaps).
+            - Be concise and direct
+            - Create inline comments for specific code issues
+            - Review comment should provide appropriate naming suggestions.
+
+          claude_args: |
+            --allowed-tools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*)"
+            --model claude-haiku-4-5-20251001
+            --system-prompt "As a software engineer with complete knowledge of the codebase, you are reviewing a pull request."

package/dist/claude/insights.yml

@@ -0,0 +1,160 @@
+name: Senior Software Engineer Code Review
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  claude:
+    if: |
+      github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude') && !contains(github.event.comment.body, '@claude-inline') && (github.event.comment.user.login == 'manufac-nmohan' || github.event.comment.user.login == 'manufac-nrawat')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Set PR/Issue number and ref
+        id: pr-info
+        run: |
+          ISSUE_NUM=${{ github.event.issue.number }}
+          echo "issue_number=$ISSUE_NUM" >> $GITHUB_OUTPUT
+
+          # Check if this is a PR comment by checking if pull_request field exists
+          HAS_PR_FIELD=$(gh api repos/${{ github.repository }}/issues/$ISSUE_NUM --jq '.pull_request != null')
+
+          if [ "$HAS_PR_FIELD" == "true" ]; then
+            PR_NUM=$ISSUE_NUM
+            echo "pr_number=$PR_NUM" >> $GITHUB_OUTPUT
+            echo "pr_ref=refs/pull/$PR_NUM/merge" >> $GITHUB_OUTPUT
+            COMMIT_SHA=$(gh api repos/${{ github.repository }}/pulls/$PR_NUM --jq '.head.sha')
+            echo "commit_sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
+            echo "is_pr=true" >> $GITHUB_OUTPUT
+          else
+            echo "is_pr=false" >> $GITHUB_OUTPUT
+            echo "pr_ref=${{ github.ref }}" >> $GITHUB_OUTPUT
+            echo "commit_sha=${{ github.sha }}" >> $GITHUB_OUTPUT
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          ref: ${{ steps.pr-info.outputs.pr_ref }}
+          fetch-depth: 0
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          claude_args: |
+            --model claude-sonnet-4-5-20250929
+            --allowed-tools "Bash(gh api:*),Write"
+            --system-prompt "As a senior software engineer with complete knowledge of the codebase and project requirements, you are reviewing a pull request."
+          prompt: |
+            REPO: ${{ github.repository }}
+            ISSUE NUMBER: ${{ steps.pr-info.outputs.issue_number }}
+            IS PR: ${{ steps.pr-info.outputs.is_pr }}
+            PR NUMBER: ${{ steps.pr-info.outputs.pr_number }}
+            COMMIT SHA: ${{ steps.pr-info.outputs.commit_sha }}
+
+            ## STEP 1: GATHER CONTEXT
+
+            1. Fetch PR files and diff:
+              `gh api /repos/${{ github.repository }}/pulls/${{ steps.pr-info.outputs.pr_number }}/files`
+
+            2. Retrieve existing comments to avoid duplication:
+              `gh api /repos/${{ github.repository }}/issues/${{ steps.pr-info.outputs.issue_number }}/comments`
+
+            3. Get PR description and metadata:
+              `gh api /repos/${{ github.repository }}/pulls/${{ steps.pr-info.outputs.pr_number }}`
+
+            ## STEP 2: DEEP ANALYSIS
+
+            Analyze the changes focusing on:
+
+            **Architecture & Design:**
+            - Does this change align with existing architectural patterns?
+            - Are there any design anti-patterns or code smells?
+            - Could this be implemented more elegantly or maintainably?
+
+            **Integration Impact:**
+            - How do these changes affect existing modules and their contracts?
+            - Are there potential breaking changes or backward compatibility issues?
+            - What are the ripple effects on dependent code?
+
+            **Performance & Scalability:**
+            - Are there performance bottlenecks (O(n²) algorithms, N+1 queries, etc.)?
+            - How will this behave under load or with large datasets?
+            - Are there memory leak risks or resource management issues?
+
+            **Security & Reliability:**
+            - Are there security vulnerabilities (injection, XSS, authentication issues)?
+            - Is error handling robust and comprehensive?
+            - Are edge cases and failure scenarios handled?
+
+            **Code Quality:**
+            - Is the code testable? Are tests adequate?
+            - Is naming clear and consistent with the codebase?
+            - Are there opportunities for code reuse or consolidation?
+
+            ## STEP 3: VERIFY PREVIOUS FEEDBACK
+
+            - Check if existing review comments have been addressed
+            - Verify that suggested changes were implemented correctly
+            - Confirm that discussions have been resolved appropriately
+
+            ## STEP 4: POST REVIEW COMMENT
+
+            Format your review as a structured comment and post it:
+            ```
+              gh api POST /repos/${{ github.repository }}/issues/${{ steps.pr-info.outputs.issue_number }}/comments -f body="[Your formatted review]"
+            ```
+
+            ## COMMENT FORMATTING GUIDELINES
+
+            **Structure your comment as:**
+
+            ### 🎯 Summary
+            [2-3 sentence overview of the changes and overall assessment]
+
+            ### ✅ Strengths
+            [Highlight what was done well - be specific]
+
+            ### ⚠️ Critical Issues
+            [Issues that must be fixed before merge - include specific solutions]
+
+            ### 💡 Suggestions
+            [Optional improvements with code examples where helpful]
+
+            ### 📊 Impact Assessment
+            - **Functionality**: [How this affects existing features]
+            - **Performance**: [Expected performance impact]
+            - **Maintainability**: [Long-term maintenance considerations]
+
+            **Writing Style:**
+            - Be specific: Reference exact files, line numbers, and function names
+            - Be prescriptive: Provide concrete solutions, not just questions
+            - Be concise: Every sentence should add value
+            - Be constructive: Frame feedback as opportunities for improvement
+            - Use code snippets to illustrate better approaches
+
+            **Prioritization:**
+            - Focus on high-impact issues first
+            - Don't nitpick trivial style issues if there are bigger concerns
+            - Group related feedback together
+
+            ## IMPORTANT CONSTRAINTS
+
+            - You MUST post your review as a GitHub comment, not just a job summary
+            - If no significant issues found, still provide a brief positive review
+            - Don't duplicate feedback already given in existing comments
+            - Tailor depth of review to the size/complexity of the PR
+            - For large PRs, focus on architectural concerns over line-by-line details
+
+            Begin your review now by fetching the necessary information.