Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .github/workflows/claude-review.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,21 @@ jobs:
with:
anthropic_api_key: ${{ secrets.anthropic_api_key }}
github_token: ${{ secrets.ai_reviewer_github_token }}
show_full_output: true
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Debugging flag exposes secrets in shared workflow logs

High Severity

show_full_output: true is enabled in a reusable workflow_call workflow shared across repositories. Per the claude-code-action docs, this flag outputs ALL Claude messages including tool execution results, which may contain secrets, API keys, or other sensitive information — and these logs are publicly visible in GitHub Actions. The PR description calls this a "pilot-phase debugging" addition, suggesting it's temporary, but it's being committed to a shared workflow consumed by many repos.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a123a62. Configure here.

prompt: |
You are a conservative AI code reviewer for an eCommerce platform (PHP, Laravel, TypeScript, React, AWS, k8s).

REPO: ${{ github.repository }}
PR NUMBER: ${{ github.event.pull_request.number }}

## Instructions
1. Run `gh pr diff ${{ github.event.pull_request.number }}` to see the full diff.
2. Analyze the changes against the criteria below.
3. You MUST submit a formal review using one of these commands:
- APPROVE: `gh pr review ${{ github.event.pull_request.number }} --approve --body "AI Review: <your summary>"`
- COMMENT: `gh pr review ${{ github.event.pull_request.number }} --comment --body "AI Review: <your summary>"`
4. If you have specific line-level feedback, post inline comments BEFORE submitting the review.

## What to Review
- Correctness and logic errors
- Security vulnerabilities (SQL injection, XSS, auth bypass, data exposure)
Expand All @@ -64,6 +76,8 @@ jobs:

If ANY concern exists, submit a COMMENT review (never REQUEST_CHANGES). Post your findings as inline comments on the relevant lines. Let the human team make the final call.

You MUST end by running one of the `gh pr review` commands above. Do not just write text — you must use the tool.

${{ inputs.review_rules }}
claude_args: >-
--max-turns ${{ inputs.max_turns }}
Expand Down