GitHub App

The GitHub App reviews changed pull-request files for security issues and suggested fixes. It provides automated review, real-time debugging assistance, security findings and an Overall Risk label. Reviews can query approved public or private knowledge bases when that capability is enabled.

Get started

Add the repository as a Pervaziv project, select the eligible branches and install the App using the button above. The App is intended for feedback on incoming pull-request changes; use the GitHub Action when you need a full-repository scan on a push or schedule.

Requirements

• An active Pervaziv Premium or Enterprise subscription
• A repository added as a project in the Pervaziv Console
• GitHub permissions to install an app and grant pull-request and issue-comment access

The App is generally available. The Marketplace plan is listed as free, but it requires the active paid Pervaziv subscription above.

Set up

1. Sign in to the Pervaziv Console and confirm the subscription.
2. Add the GitHub repository as a project.
3. Select the target branch that AI Code Review may review.
4. Install the GitHub App for only the repositories Cortex should access.

The App is automatically enabled for the configured project. GitHub organization policy may require owner approval. If a repository is missing, check both the App installation’s repository selection and your GitHub access.

Review experience

The App analyzes the changed files at the pull request’s current head. Review feedback can include a summary, findings, eligible inline suggestions and an Overall Risk label. A manual review can be requested with /pervaziv-ai review; /pervaziv-ai help exposes the supported bot commands.

This keeps the security discussion attached to the change developers are reviewing. The label supports triage, while the findings identify the code that needs investigation. See review a pull request for the review and follow-up sequence.

Remediation and project controls

Suggested fixes are inputs to the developer’s review. Inspect the diff and validate the updated revision before using an earlier result to justify a merge. Code changes can alter the scope of the original finding.

The connected project exposes automatic update, code suggestion, AI scan and allowed-branch controls. GitHub installation permissions and Pervaziv project settings both affect whether a repository or branch can be reviewed.

Where the App fits in a team’s review

The App gives reviewers security-oriented feedback without moving the entire discussion to another platform. Changed-file analysis connects the finding to the proposal under review; the Overall Risk label offers a quick triage signal; eligible suggestions provide a candidate remediation to inspect.

Use the findings to ask focused questions about the change: what input reaches the affected code, what permission should be checked, and what test would demonstrate that a suggested fix preserves the intended behavior? The App’s output supports the reviewer, rather than replacing the team’s merge policy.

Scope and follow-up

Because the App reviews pull-request changes, use the separate repository Action when the goal is a baseline across files outside the diff. Connect the Console report when broader project security context is needed. After the author updates the pull request, review results for the current head and validate the modified behavior before accepting the suggestion.

The public launch describes automated review, debugging assistance, security findings and generative remediation for supported languages. Exact coverage depends on the changed files, available context and configured analysis.

Product background

Introducing AI Code Review for pull requests describes the App’s role; the GitHub Action launch explains the separate repository assessment.

Access management

Remove access from both the Pervaziv project and GitHub App installation when the integration is no longer needed. The Marketplace listing contains the current public plan and permission summary.