PatchPatrol by aistack
Review GitLab merge requests through a model endpoint you control. PatchPatrol also supports GitHub Actions and local diff reviews.
PatchPatrol by aistack
Concept
Transparent AI use
PatchPatrol sends selected review context only to the model endpoint you configure. You can also restrict calls with an endpoint allowlist. If that endpoint is remote, the provider receives the selected content under its own data-handling terms.
Configured endpoint, optional allowlist
Limited context
PatchPatrol limits changed files, changed lines, diff size, and any supporting context before review.
MR, GitHub PR, and local diff context
Directly traceable
Depending on your setup, PatchPatrol publishes a compact GitLab Review Summary. Priority Findings appear as inline discussions on the affected lines. The HTML Run Report contains the full record of the run. Reviewers can quickly see what needs a closer look.
GitLab Review Summary, inline findings, HTML Run Report
Risk in focus
PatchPatrol surfaces signals that deserve attention and adds context for the affected change.
Context for decisions
Repository-aware rules
For individual paths, components, and file types, teams can define targeted review guidance. PatchPatrol checks changes against your project's standards instead of relying only on generic review logic.
Technical documentation.ai-review.yml
Pipeline integration
PatchPatrol extends your existing merge request or pull request pipeline. Feedback appears directly in the CI run so reviewers can see which changes need attention.
Uses existing tools from your project
GitLab CI
How it works
Step 01
The run starts with a concrete change: a GitLab merge request, a GitHub pull request workflow, or a local diff.
Step 02
Configured limits cap changed files, changed lines, diff size, and any supporting context before the provider call.
Step 03
Before provider calls, PatchPatrol applies configured review bounds and optional endpoint restrictions. It applies pattern-based redaction to extracted diff chunks and fails closed on detected high-confidence patterns.
Step 04
The LLM checks the change context, scope limits, and affected code paths. The result is a set of prioritized findings with clear reasoning.
Step 05
PatchPatrol validates the model response before publishing any feedback. The compact GitLab Review Summary shows what needs a closer look. Priority Findings appear as inline discussions on the affected lines, while the HTML Run Report contains the full record of the run.
Documentation
Start with the GitLab setup, or open the configuration reference for providers, variables, and review limits.
GitLab pipeline
The admin quickstart shows how to prepare providers and GitLab CI, then run the first artifact-based merge-request review.
Open admin quickstartConfiguration
Use the configuration reference to set providers, environment variables, review limits, and report output for production.
Open configuration referenceNext step
Tell us about your GitLab review job, the model endpoint you plan to use, and what PatchPatrol needs to prove in your environment. We will reply with evaluation and pricing information. Product access and any pilot are agreed separately.
