Skip to content
ThinkReviewThinkReview Docs

Custom Rules

Custom rules let you encode team-wide review standards—naming conventions, security policies, architecture patterns, and domain guidelines—so ThinkReview applies them automatically on every PR or MR.

Configure them in the ThinkReview portal under Custom Rules.

What custom rules are for

Section titled “What custom rules are for”
  • Keep reviews consistent across junior and senior developers
  • Prioritize the security and quality checks your org actually cares about
  • Align AI findings with existing coding standards instead of a generic checklist

You select security checks and best-practice checks (including your own). ThinkReview injects those preferences into the review prompt so the model prioritizes them in findings.

Where rules apply

Section titled “Where rules apply”

Custom rules apply to both review layouts and both review entry points:

Surface How rules are used
Scoring layout Findings call out matching issues, and scores deduct extra points for violations.
Severity layout Matching issues are prioritized in findings and treated as higher severity when warranted.
Browser extension Rules are included on every patch review, in both layouts.
URL / MCP review Rules are included on URL-based reviews (including MCP’s default severity layout).

Rules require flagship models available on Lite, Professional, and Teams. Free-plan models do not apply custom-rules customization.

How to set up custom rules

Section titled “How to set up custom rules”
  1. Sign in to the ThinkReview portal.
  2. Open Custom Rules (/custom-rules; older /scoring-metrics links redirect here).
  3. Select up to 10 security checks and up to 10 best-practice checks (predefined or your own).
  4. Save your preferences, then open any pull or merge request on a supported platform and run ThinkReview—or run a URL review from MCP.

Rules apply from the extension sidebar and from MCP—no CI job or admin install is required.

Tips

Section titled “Tips”
  • Start with a short list of high-signal rules (security and must-fix conventions) before expanding.
  • Pair rules with Review Agents when you need specialized checklists (for example OWASP-focused security) in addition to global standards.
  • After changing rules, use Refresh or a new commit to regenerate a review with the updated preferences.
Section titled “Related”

TL;DR: Custom rules encode your team’s review standards in the portal so every ThinkReview analysis—scoring or severity, extension or MCP—follows them. No pipeline changes required.