Skip to main content

​
General

Gitar is an AI code review and CI fixing agent that works directly in your PR interface. It reviews code changes for security, bugs, and performance issues, analyzes CI failures, and pushes fixes without you leaving the pull request. See How Gitar Works for a detailed overview.
When a PR is created or updated, Gitar reads the diff, the full files touched by the change, CI logs if CI fails, and any configured repository rules. It then reviews the code, identifies issues, and can push fixes directly to your branch.Findings are posted as inline review comments on the relevant lines. The Gitar dashboard comment on the PR carries a consolidated summary of review, CI analysis, and rule results. See How Gitar Works for the full breakdown.
Gitar is language-agnostic. It works with any programming language or framework. Code review, CI failure analysis, and fix generation all operate on the code as-is, regardless of the language.
Yes, on Enterprise. Gitar can serve every LLM call from your own Anthropic, AWS Bedrock, or gateway account, and your provider bills you directly. See Bring Your Own Model and Plans.

​
Security & Privacy

Through OAuth integrations with GitHub and GitLab. Gitar accesses only the repositories you configure and performs only the maintenance tasks you approve. Repository access is logged and auditable. See Security for full details.
No. Code is processed in ephemeral environments that are destroyed when the task completes. Gitar holds zero data retention agreements with every AI provider it uses, so your code is never stored or used for training.
No. Gitar does not use customer code for training AI models. Your code stays private and serves only the maintenance tasks you request.
Secrets encountered during processing are not logged, stored, or transmitted outside the processing environment. They exist only in encrypted memory for the life of the environment and are erased when it is destroyed.
Gitar maintains security controls aligned with SOC 2 Type II and ISO 27001. Third-party assessments run regularly. Contact security@gitar.ai for current attestation status.
Gitar holds contractual zero data retention agreements with every AI provider it uses, including Google and Anthropic. Under those agreements no customer code is retained, stored, or used for model training, and processing runs against zero-retention API endpoints.
Organizations are isolated at the database, application, and infrastructure levels. No organization can access another’s data, configurations, or processing environments.

​
Code Review

Open your organization settings in the Gitar dashboard, find the Code Review section under Features, and enable the toggle. Gitar then reviews all new PRs automatically. See Code Review for details.
Yes. Add markdown files to the .gitar/review/ directory in your repository with custom instructions, checks, or gotchas. Gitar reads these during review to tailor feedback to your project. See Repository Customization for the full setup.
Reply to the inline review comment to explain why a fix is unnecessary, or resolve the thread on GitHub. Gitar tracks findings closed without a fix separately from findings resolved by a code change.Pushing code that addresses the issue resolves the finding on its own: the inline thread closes and the finding moves to the collapsible “Resolved” section of the dashboard comment. Dismissals persist across review iterations, so Gitar won’t re-raise issues you have already closed out.
On GitHub, check the box next to the suggested fix in the inline comment. On GitLab, react with the checkmark emoji. Gitar commits the fix directly to your branch. If a finding has multiple suggested fixes, each one is numbered so you can pick the right one.
The full repository, not the PR diff alone. Gitar follows imports, checks call sites, and traces how your change connects to the rest of the codebase, which is how it catches broken callers, inconsistent patterns, and missing updates in related files.
Linters and SAST tools match predefined patterns: style violations, known vulnerability signatures, and static rule violations. Gitar reasons about the intent behind your change in context, so it can flag incorrect logic, unhandled edge cases, and drift from the rest of the codebase.The two are complementary. Run both, and let Gitar cover what pattern matching cannot reach.
A pull request holding a single commit that reverts an earlier one is skipped, as that commit was already reviewed when it went in. The dashboard comment says so rather than leaving a gap. Push any commit beyond the revert and Gitar reviews the pull request as usual.
Copilot code review works on the PR diff with limited repository context. Gitar explores the full codebase, following imports and checking call sites to reason about how your change affects the rest of the project.Gitar also pushes fixes directly to your branch, analyzes and fixes CI failures, takes custom review instructions and rules, and re-reviews after every push so findings stay current as the PR evolves.

​
CI Failure Fixing

Gitar handles build errors (compilation failures, missing imports, type errors), test failures (broken assertions, missing setup), linting errors (code style violations, formatting issues), and flaky tests (race conditions, timing issues). See CI Failure Analysis for the full list.
If Gitar cannot resolve a failure after multiple iterations, it posts a summary of what was attempted so you have full context to debug manually. You can also comment with additional context to steer Gitar’s next attempt.
Recovery is bounded. The conditions and stopping points are described in CI Failure Analysis. A fresh comment can provide more context when another attempt is needed.

​
Billing & Plans

Visit your billing settings at app.gitar.ai and select a plan. Your trial features continue uninterrupted once you subscribe. See Managing Your Subscription for details.
Without an active subscription, the organization returns to the Free plan. Code reviews and PR commands require a plan that includes them. The trial runs 14 days. See Plans for available features.
Yes. You can upgrade between Core and Pro at any time from your billing settings. To move to an Enterprise plan, contact support@gitar.ai. Enterprise plans include unlimited seats, custom integrations, and dedicated support.
Use the cancellation controls in billing settings for a self-serve subscription. Access continues until the end of the current billing period. See Managing Your Subscription for the steps and Enterprise support path.
Yes. Vetted open-source projects get Gitar free on the Open Source plan, which includes everything in Pro plus unlimited seats. It covers public repositories on github.com or gitlab.com, and each repo is approved individually. Apply through the Gitar for OSS application form. See Plans for eligibility and details.

​
Integrations

Connect as many ticket trackers as you use. A bare key like PROJ-123 looks identical across all four, so Gitar attributes it by precedence: Jira first, then Linear, then Plane, then YouTrack. An org running two trackers never resolves a bare key to the second one. See Jira, Linear, Plane, or YouTrack for setup instructions.

​
Troubleshooting

Gitar not responding to your comments, or CI still failing after its fixes? Both are covered in Troubleshooting. See also Commands & Interactions for how to address Gitar.
The organization has used its automatic-processing headroom for the billing period. On paid plans, reviews on new PRs and comment-triggered work continue, while automatic re-reviews after pushes pause.Comment “Gitar review” to request another review, subject to the plan and seat requirements. Headroom resets with the next billing period and scales with assigned seats.See Plans & Billing for more details.
Your organization is on a paid plan (Core or Pro) and no admin has allocated a seat to your account yet.
  • Ask a team admin to assign you a seat from the organization settings at app.gitar.ai
  • During a trial period, seats are not enforced and all members have full access
See Plans & Billing for more details.
Use gitar-skip to skip automatic processing for that PR. Explicit comment commands still work.