code-review

To review a GitHub pull request for security and quality compliance, invoke the code review Skill with the specific PR number. It categorizes issues by severity tiers, ensuring risky credential and workflow changes are caught before merging.

Running a dry-run code review on your current branch is best achieved by explicitly invoking the code review Skill without a PR argument. This generates a local report classifying diff changes against security and quality rubric compliance tiers.

Diff analysis handles large pull requests by classifying changed files into tiered strategies. This controls how much file content is read, improving the review signal while maintaining consistent behavior and preventing truncation issues.

Yes, you can use automated code review for NetSuite workflow and script changes. The Skill evaluates modifications across the repository, applying security checks and rubric compliance specifically designed for NetSuite skill development.

If a pull request is in an invalid state during a security check, the code review enforces fail-closed behavior. It applies defensive checks, including skip conditions and PR-head path mapping, to avoid being misled by untrusted content.

Yes, code review works with Claude Code to analyze pull requests. It safely materializes PR-mode diffs with path mapping, ensuring the diff analysis accurately reflects the changes without exposing the system to untrusted repository content.