review-patch

To get structured code review feedback on a Gerrit patch, provide the specific change ID. The system retrieves modified files, diffs, and commit messages to evaluate code quality, security, and testing adequacy.

Yes, you can evaluate commit messages and existing inline comments during a Gerrit code review. The process fetches existing review comments and commit messages to ground the feedback in what has actually changed.

Automated security and code quality feedback for incoming patches includes a structured review covering patch intent, commit message quality, code quality, security concerns, and testing adequacy based on file diffs.

Yes, reviewing Gerrit changes requires Gerrit MCP access to retrieve change details, file lists, per-file diffs, existing comments, and commit messages so the review can be properly organized into structured sections.

To analyze diffs for security concerns and project convention expectations, the system fetches per-file diffs and existing inline comments, generating a consistent review that highlights whether the patch meets established quality standards.

Automated static inspection for Gerrit patch review is limited to analyzing provided diffs, commit messages, and existing comments. It cannot execute code or perform dynamic runtime security testing outside the available diff context.