Skip to main content
As more code is written by agents, reviewing it becomes the bottleneck. Indent can review pull requests with full repository context, post findings directly on GitHub, and keep the fix loop close to the PR so nothing falls through the cracks. Best with: Environment Setup and clear repository guidance in AGENTS.md, Skills, or .indent/rules/*.mdc.

​
Setting up review

Review is configured per repository from the review dashboard. For each repo you can control:
  • Review all PRs — when enabled, Indent reviews PRs that are labeled indent, that @mention the bot, or that come from included authors. Disable this to only review on demand.
  • Included / excluded authors — allowlist specific contributors for automatic review, or exclude authors whose PRs should never be reviewed.
  • Ignore draft PRs — skip drafts and start reviewing when the PR is marked ready.
  • PR summary comment — post a top-level comment on the PR summarizing changes and potential issues.
  • CI failure summary — post a comment explaining CI failures with suggested fixes.
You can start narrow — a single repo, a few included authors — and widen coverage as your team gets comfortable.

​
What Indent posts on a PR

When Indent reviews a PR, it posts a single top-level comment with the following sections:
  • Issues — problems found in the diff, categorized as Critical, Recommended, or Nit. Previously resolved issues are collapsed so the comment stays focused on what still needs attention.
  • Summary — a description of what the PR does, broken down by intent rather than by file, so reviewers can understand the change quickly.
  • CI Checks — if any CI jobs failed, Indent explains the failure and calls out whether it looks PR-related or like an infrastructure flake.
  • Rule Checks — results from any review rules configured for the repo (see below), showing which rules passed and which flagged issues.
At the bottom of the comment, an Autofix All button lets you apply all auto-fixable suggestions at once.

​
Continue the conversation in-thread

Reply to any of Indent’s review comments or mention @indent to go deeper — ask it to explain a concern, suggest a different approach, or justify why the current code is correct. The conversation stays in the same GitHub thread, visible to everyone on the PR. This isn’t a one-shot report. Your team can treat Indent like another reviewer you can push back on, ask follow-ups, and reach a resolution with — all without leaving GitHub.

​
Autofix

When a finding is straightforward to fix, click Autofix to apply the change as a new commit. Use Autofix All to resolve every auto-fixable finding at once. If the PR is attached to an Indent session, fixes flow back into chat so the session can pick up the next step. Indent won’t autofix anything complex or ambiguous — it only acts when the fix is clear-cut.

​
Review rules

Review rules let you encode your team’s standards so Indent checks for them on every review. You can configure rules in two ways:
  • From the review dashboard — add and edit rules under each repository’s settings in the review dashboard. See Set Up PR Review for a walkthrough.
  • Committed to your repository — add .mdc files under .indent/rules/ in your repo. This is useful for versioning rules alongside your code.
Each rule has:
  • Title — a short name like “Database Migration Safety” or “Security Guidelines.”
  • Rule — a description of what to check for.
  • When to use (optional) — additional context about when the rule applies.
  • File patterns — glob patterns that scope the rule to specific files (e.g., **/migrations/*.py). Leave empty to apply to all files.
Here’s an example of a rule committed to a repository: 
---
description: Security review guidelines
globs: "**/auth/**, **/tokens/**, **/secrets/**"
when_to_use: When reviewing security-sensitive code
---

# Security Guidelines

- Never log secrets, tokens, or API keys
- Validate all user input before processing
- Use parameterized queries for database operations
- Check authorization before performing sensitive operations
Rule results appear in the Rule Checks section of the PR comment, so your team can see at a glance which standards passed and which need attention.