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 rules and related scoring preferences in the ThinkReview portal.

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

Custom rules work together with the Scoring System. When you calibrate security checks and best-practice guidelines, ThinkReview injects those preferences into the review and scores accordingly.

How to set up custom rules

Section titled “How to set up custom rules”
  1. Sign in to the ThinkReview portal.
  2. Open scoring metrics / custom rules settings (the same area used to calibrate security and best-practice checks).
  3. Define the standards your team expects on every review—naming, security policies, domain patterns, and related guidelines.
  4. Save your preferences, then open any pull or merge request on a supported platform and run ThinkReview.

Rules apply from the extension sidebar—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 follows them—no pipeline changes required.