- The reviewer follows your existing conventions. It loads the convention files already in your repository on demand, so it reviews against the same standards your coding assistants already use.
- The reviewer learns from past reviews. The issues your team keeps running into, and keeps fixing, become reusable rules that the reviewer applies to future PRs on its own.
How it works
- Your existing convention files. Point the reviewer at the coding-assistant convention files your team already maintains, such as
CLAUDE.md,.claude/rules/,AGENTS.md, or.cursorrules. The reviewer loads them on demand during each review, so there’s nothing to author. - Rules learned from past reviews. On a schedule you choose, CloudThinker looks at the review findings your team has already resolved on a repository, turns the recurring ones into named rules, and applies those rules in later reviews. You review the results from the Conventions page.
Use your existing convention files
In Code Review → Settings, find the repository and select the Convention Rules icon under Actions.
Open Convention Rules from the repository’s actions
Choose the coding assistant tool your team uses in the Convention Rules dialog:
Select the coding assistant whose convention files the reviewer should follow
Select Save. The AI reviewer automatically finds and reads the matching convention files during each review.Just select your convention rules tool. The AI reviewer finds and reads the convention files in your repository for you, so there’s no need to specify exact file paths.
Supported tools
Custom convention paths
You can add Custom Convention Paths to point the reviewer at additional convention files or directories in your repository. This is useful when your team keeps convention files in non-standard locations or uses more than one tool. Click + Add path in the Convention Rules dialog to specify relative paths to additional convention files or directories.Rules learned from past reviews
CloudThinker learns your team’s coding conventions from each repository’s default branch and applies them in future reviews. As your team resolves review findings, the recurring ones become named rules. New rules show up on the Conventions page after the next scheduled run, so the reviewer keeps catching the issues your team cares about without anyone writing rules by hand.Until the first run finishes, the Conventions page is empty. Rules appear on their own after the next scheduled run for the repository, once it has enough resolved review findings to learn from.
Set the update schedule
Rule updates run per repository on a cadence you choose. In Code Review → Settings, use the Convention Rules column to pick how often CloudThinker refreshes a repository’s rules:
Choose how often CloudThinker updates learned rules for a repository
Weekly runs happen every Saturday, in either the 00:00 UTC or the 12:00 UTC hour — after the work week, so updated rules are in place before Monday’s reviews. CloudThinker assigns your repository one of those two times and keeps it, so runs land at the same time every week. Monthly runs use the same time on the first Saturday of the month. The Convention Rules column shows the next scheduled run.
The first run does not wait for the weekend. When you turn the schedule on for a repository, the first run starts soon after, so the first week can contain two runs: that first one, then the repository’s regular Saturday run. The second run only covers findings resolved since the first.
Review learned rules
Open Conventions under Code Review to review learned rules. Rules are generated automatically; from this page, you can read them, filter the list, and turn individual rules on or off.
Review learned rules and control which ones are active
Keep an eye on the Cited count. It shows which conventions your team runs into most, so you can tell at a glance what matters and decide which rules to keep, fix at the source, or turn off.
Filters at the top of the table help you find rules:
- Search by slug or title.
- Repository to focus on one or more repositories.
- Status to show only Active or Disabled rules.
Read a rule
Click a row to open the complete rule. The detail view shows the rule’s category, identifier, citation count, description, guidance, and examples. You can also change its active status from this view.
Open a learned rule to read its full guidance
Permissions
Viewing rules and changing their schedule or active status use separate workspace permissions. Without view access, the Conventions page asks you to contact your workspace admin. With view-only access, you can read rules, but the schedule and Active controls are disabled. Ask a workspace admin for access to change the schedule or turn rules on and off.FAQ
Do I need convention files if CloudThinker learns rules for me?
Do I need convention files if CloudThinker learns rules for me?
No. The two work independently, so you can use either or both. Convention files are read right away; learned rules build up from your reviews over time.
Why don't any rules appear yet?
Why don't any rules appear yet?
Rules show up after the first scheduled run for a repository. Make sure Code Review is enabled, the repository has finished cloning, and the Convention Rules schedule is set to Weekly or Monthly rather than Off. A new repository also needs enough resolved review findings before the first rules appear.
Why is the schedule dropdown greyed out?
Why is the schedule dropdown greyed out?
The schedule turns on once Code Review is enabled, the repository has finished cloning, and you have permission to change its Convention Rules schedule.
Can I stop a rule without losing it?
Can I stop a rule without losing it?
Yes. Turn the rule off in the Active column. It stops applying to reviews right away, and you can turn it back on at any time.
Related
Code Review setup
Connect your repositories for automated code review
Extensions
Pull issue-tracker context into reviews automatically