Code review comment generation via retrieval-augmented transformer with chunk cross- attention
US-2024184570-A1 · Jun 6, 2024 · US
US2025335185A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025335185-A1 |
| Application number | US-202418648080-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 26, 2024 |
| Priority date | Apr 26, 2024 |
| Publication date | Oct 30, 2025 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some implementations, a device may obtain an indication of a proposed change to a subset of executable code from a set of executable code. The device may determine, via one or more models, first context information associated with the proposed change and second context information associated with at least one of the subset of executable code, the set of executable code, or a context of the subset of executable code within the set of executable code. The device may determine a scrutiny level for review of the proposed change based on at least one of the first context information or the second context information. The device may obtain, via the one or more models, review information associated with the proposed change, wherein the one or more models apply the scrutiny level to obtain the review information. The device may perform an action based on the review information.
Opening claim text (preview).
What is claimed is: 1 . A system for automated code review using artificial intelligence (AI), the system comprising: one or more memories; and one or more processors, communicatively coupled to the one or more memories, configured to: obtain a pull request indicating a proposed change to a subset of executable code from a set of executable code; determine, using one or more AI models, first context information associated with the proposed change and second context information associated with at least one of the subset of executable code, the set of executable code, or a context of the subset of executable code within the set of executable code; generate an embedding vector representing at least one of the first context information or the second context information; determine, using the embedding vector and an embedding space, a scrutiny level for review of the pull request based on at least one of the first context information or the second context information; obtain, via the one or more AI models and using the scrutiny level, review information associated with the pull request; and perform, based on the review information, an action to modify the proposed change or to commit the proposed change to the set of executable code. 2 . The system of claim 1 , wherein the review information includes at least one of: natural language text indicating a review of the proposed change, or proposed executable code to be included in the proposed change. 3 . The system of claim 1 , wherein the one or more AI models include at least one of: a first model configured to output the first context information, a second model configured to output the second context information, or a third model configured to output the review information. 4 . The system of claim 1 , wherein the scrutiny level indicates a level of review to be applied by the one or more AI models when reviewing the pull request. 5 . The system of claim 1 , wherein the scrutiny level is indicated to the one or more AI models via at least one of: a setting of the one or more AI models, a hyperparameter of the one or more AI models, or a prompt input to the one or more AI models. 6 . The system of claim 1 , wherein at least one of the first context information or the second context information indicates a level of impact of the proposed change to the set of executable code, and wherein the one or more processors, to determine the scrutiny level, are configured to: determine the scrutiny level based on the level of impact of the proposed change to the set of executable code. 7 . The system of claim 1 , wherein the one or more processors are further configured to: generate, using at least one of the first context information or the second context information, the embedding vector to represent the proposed change in context of the set of executable code; and wherein the one or more processors, to determine the scrutiny level, are configured to: determine the scrutiny level based on a location of the embedding vector in the embedding space. 8 . The system of claim 1 , wherein the one or more processors are further configured to: generate, using at least one of the first context information or the second context information, a profile representing the proposed change, wherein the profile indicates one or more parameters of the proposed change; and wherein the one or more processors, to determine the scrutiny level, are configured to: determine the scrutiny level using the profile. 9 . The system of claim 8 , wherein the one or more processors, to determine the scrutiny level, are configured to: generate another embedding vector that represents the profile; identify, in the embedding space, a nearest neighbor embedding vector to the other embedding vector; and determine the scrutiny level based on another scrutiny level that was applied for another profile that is represented by the nearest neighbor embedding vector. 10 . The system of claim 1 , wherein the one or more processors, to perform the action, are configured to: generate a reviewed pull request indicating a reviewed change to the subset of executable code, wherein the reviewed change incorporates the proposed change and the review information; and cause the reviewed pull request to be merged with the set of executable code. 11 . A method for automated code review, comprising: obtaining, by a device, an indication of a proposed change to a subset of executable code from a set of executable code; determining, by the device and via one or more models, first context information associated with the proposed change and second context information associated with at least one of the subset of executable code, the set of executable code, or a context of the subset of executable code within the set of executable code; determining, by the device, a scrutiny level for review of the proposed change based on at least one of the first context information or the second context information; obtaining, by the device and via the one or more models, review information associated with the proposed change, wherein the one or more models apply the scrutiny level to obtain the review information; and performing, by the device, an action based on the review information. 12 . The method of claim 11 , wherein the one or more models include at least one of: a first one or more models configured to output at least one of the first context information or the second context information, or a second model configured to output the review information. 13 . The method of claim 11 , wherein obtaining the review information comprises: providing the scrutiny level as an input to the one or more models. 14 . The method of claim 11 , further comprising: generating, using at least one of the first context information or the second context information, an embedding vector that represents the proposed change in context of the set of executable code; and wherein determining the scrutiny level comprises: determining the scrutiny level based on a location of the embedding vector in an embedding space. 15 . The method of claim 11 , further comprising: generating, using at least one of the first context information or the second context information, a profile representing the proposed change, wherein the profile indicates one or more parameters of the proposed change; and wherein determining the scrutiny level comprises: determining the scrutiny level using the profile. 16 . The method of claim 11 , wherein the one or more models include a model configured to output the review information, and wherein the model is trained using account information of an account that is associated with the proposed change. 17 . The method of claim 11 , wherein the one or more models include a large language model configured to generate and output the review information. 18 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the device to: obtain a pull request indicating a proposed change to a subset of executable code from a set of executable code; determine, using one or more artificial intelligence (AI) models, first context information associated with the proposed change and second context information associated with at least one of the subset of executable code, the set of executable code, or a context of the subset of executable code within the set of e
Analysis of software for verifying properties of programs (testing of software G06F11/3668) · CPC title
using software metrics · CPC title
Program documentation · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Structural analysis for program understanding · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.