Getting Started
An overview of what Greptile can do
Greptile’s code review bot does three things:
Summarizes Changes
Greptile summarizes the changes in the pull/merge request
Comments on Issues
Greptile comments on specific file changes and suggests potential issues and unforeseen consequences of the change.
Suggests Fixes
Greptile suggests potential fixes for issues and unforeseen consequences of the change.
What does Greptile comment on?
Greptile comments on many types of bugs, antipatterns and style violations out-of-the-box, and can be configured to enforce your custom rules.
You can think of Greptile as a stack-agnostic, AI-powered linter.
Logic
Surfaces logical errors by inferring the intent of the change and scanning related files, imports, and more.
Style
Enforces stack-specific best practices as well as your custom style guide and patterns.
Performance
Identifies potential performance issues by analyzing the impact of the changes on the codebase.
Security
Identifies potential security issues by analyzing the impact of the changes on the codebase.
Compliance
Enforces your custom compliance rules and regulations.
Code Repetition
Identifies potential code repetition by scanning the codebase for similar code.
Why is it useful?
Greptile’s code review bot writes comments that:
- Are context-aware, so can discuss the implications of the changes to the wider codebase.
- Can identify potential performance,security or compliance issues produced by the changes.
- Reference similar code or abstractions related to the changes that are already in the codebase, to prevent repitition.
- Enforces your custom style guide and prescribed patterns.
This means:
- Less time spent reviewing PRs or awaiting review, and more time spent writing code.
- More bugs caught that humans might miss.
- A human reviewer can focus on the “big picture” and “strategic” aspects of the changes, while the bot can focus on the “tactical” aspects.
Click here to see a sample PR review on twentyhq/twenty! ->
Was this page helpful?