Claude Code Security Review — PR Audit Action

Practical Notes

• Diff-aware mode: README says it analyzes changed files for PRs (not full repo)
• Default model input in README references Opus 4.1 and a 20-minute ClaudeCode timeout (configurable)

Using It Without Shooting Yourself in the Foot

AI security review is most useful when it’s diff-scoped and the repo has clear trust boundaries.

Recommended rollout:

• Enable it on internal PRs first (or require maintainer approval for external contributors) to reduce prompt-injection risk.
• Treat findings as a review aid, not an automatic block, until you calibrate false positives.
• Keep the action’s permissions minimal: it needs PR comment write access, not repo write access.

The README also documents customization via files (for example custom scan instructions and false-positive filtering). Adopt that once your team agrees on a “house style” for security comments.

FAQ

Q: Does it scan the whole repo? A: For PRs it focuses on changed files/diffs (per README).

Q: Is it hardened against prompt injection? A: The README explicitly warns it is not; use trusted PR policies.

Q: How do I tune false positives? A: Use the provided inputs for custom instructions / filtering files.