Alibaba Cloud DevOps Adds Review Memory for Team-Specific Code Rules

Turning review explanations into reusable rules

Intelligent Code Review can identify common code issues, but Alibaba Cloud says that reliable reviews also require an understanding of a repository's technical constraints, business rules and team preferences. Review Memory captures context that has already been clarified during reviews and applies it to relevant future changes.

The feature is intended to preserve rules that might otherwise depend on individual team members' knowledge. Examples include interfaces used by legacy systems, established exception-handling practices and related logic that must be updated when a particular field changes.

Teams can add a memory by telling Intelligent Code Review in a merge request comment what they want it to remember. The system then organizes the information into a candidate memory for the current repository. Once the memory takes effect, future reviews automatically use it when evaluating relevant changes.

Four types of repository context

Alibaba Cloud identifies four categories that are particularly suitable for Review Memory: repository rules, business constraints, team preferences and risk-related experience. Repository rules can describe conventions that apply to particular packages, modules, classes or interfaces. Business constraints can cover legacy compatibility paths, fields in external systems and staged rollout requirements.

Team preferences include long-standing implementation approaches, naming styles and exception-handling strategies. Risk-related experience covers types of changes that have historically caused problems and require additional checks.

The company gives several examples. A team can record that a database automatically updates modification timestamps, preventing future reviews from treating the lack of manual assignment as an omission. In an e-commerce application, it can also specify that courier deliveries require a shipping address, while in-store pickup requires a selected pickup store instead.

Another example concerns DTOs in a compatibility package. A rule can require classes whose names end in DTO to retain a public no-argument constructor because a legacy compatibility path creates objects through reflection.

Internal test reported fewer incorrect comments

Alibaba Cloud says its DevOps team built a test set and conducted comparative tests to assess whether Review Memory could reduce incorrect comments caused by missing information, limited repository context or unfamiliarity with team conventions. On the samples in that internal test set, using Review Memory reduced incorrect review comments by 96.9%.

The company explicitly says that 96.9% is a reduction in incorrect comments on the internal test set, not an overall accuracy rate for all repositories and review scenarios. Alibaba Cloud says the intended effects include fewer low-value distractions, less repeated explanation of team conventions and more consistent reviews based on the same repository rules.

The source also stresses that long-term memories need governance. Repository administrators can enable or disable Review Memory through Repository Settings, AI Assistant Settings, Intelligent Code Review, Review Memory. Administrators can also enable memory approval, after which newly generated candidate memories must be confirmed by an administrator before they take effect. This gives teams a way to review, revise and disable repository context rather than allowing every one-off explanation to remain active indefinitely.