Code auditing method and device, project code development method and terminal equipment
Through the automated code review process, the preset review model is determined using code language information, which solves the problem of cumbersome existing code review process and achieves more efficient and quality code review.
Patent Information
- Application Number
- CN202510022914.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-07
- Publication Date
- 2025-04-18
AI Technical Summary
The existing code review process is cumbersome, which affects the review efficiency.
By obtaining the code configuration file when triggering the code change event, determining the preset code review model based on the code language information, automatically inputting the code change content and model prompt words for review, and sending the model review results to the architect user side.
No need to manually identify code language types, save workload and time, and improve code audit efficiency and quality.
Smart Images
Figure CN119847906A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of code development, and in particular to a code review method and device, a project code development method and terminal equipment. Background Art
[0002] In a multi-person development project, different technicians have different coding habits and development capabilities. In order to improve the quality of project code, code review is an important link. Usually in a project, the architect needs to undertake the work of code auditing. After the technician modifies the code, he will submit the modified results. After the relevant personnel identify the language type of the code, it will be sent to the corresponding architect. For example, if it is Java language, it will be sent to the back-end architect; if it is H5, it will be sent to the front-end architect; if it is IOS, it will be sent to the mobile architect, etc. The architect will then check the quality of the technician's code and make reasonable modification suggestions. However, this code review process is relatively cumbersome and will affect the overall review efficiency of the code review link. Summary of the invention
[0003] The present invention application provides a code review method and device, a project code development method and terminal equipment, which can improve the overall review efficiency of the code review link.
[0004] In order to solve the above technical problems, the first aspect of the present invention application provides a code review method, comprising:
[0005] When a code change event is triggered, a code configuration file of a target project is obtained, wherein the code configuration file includes model prompt words, code change content, and code language information;
[0006] Determine a corresponding preset code review model according to the code language information, and input the code change content and the model prompt word into the preset code review model to obtain a model review result of the target project;
[0007] The corresponding architect user terminal is determined according to the code language information, and the model review result is sent to the architect user terminal so that the architect user terminal can review the model review result and obtain the target review result.
[0008] In the first aspect of the application of the present invention, when a code change event is triggered, a code configuration file is obtained, the code configuration file includes a model prompt word, code change content and code language information; the corresponding preset code review model is determined according to the code language information, and there is no need to manually identify the language type of the code and select the architect to review, which can save a certain amount of workload and time; the code change content and model prompt word are input into the preset code review model to obtain the model review result, and after determining the corresponding architect user end according to the code language information, the model review result is sent to the architect user end for further review, which provides a reference for the architect user's review work, reduces the time spent by the architect user on code review work, and can effectively improve the overall review efficiency and quality of the code review process.
[0009] A second aspect of the present invention application provides a project code development method, comprising:
[0010] Creating a target project and constructing a project flow of the target project; the project flow includes one or more code review nodes, and the code review nodes are used to execute the code review method;
[0011] Obtaining a target review result based on the execution result of the code review method by the code review node;
[0012] When the target review result is approved, the project process is updated.
[0013] In the second aspect of the application of the present invention, when developing the code of the target project, a target project is created and its project process is constructed, wherein the process includes one or more code review nodes, and the development or change of the code in the project process is reviewed through the code review nodes. During the code review, the corresponding preset code review model is determined according to the code language information, and there is no need to manually identify the language type of the code and select the architect for review, which can effectively save manpower and material resources in the process of target project code development; and after the model is reviewed, the model review result is sent to the architect user end for further review, which can provide a reference for the code review work of the architect of the target project and reduce the time spent by the architect on the code review work; in addition, the target review result is obtained based on the execution result of the code review node, and the project process is updated when the result is approved, which can effectively reduce the time spent by the target project in the code review link, shorten the project cycle and improve the code development efficiency of the project.
[0014] The third aspect of the present invention application provides a code review device, including an acquisition module, a review module and a first sending module; wherein,
[0015] The acquisition module is used to acquire a code configuration file of a target project when a code change event is triggered, wherein the code configuration file includes model prompt words, code change content, and code language information;
[0016] The review module is used to determine the corresponding preset code review model according to the code language information, and input the code change content and the model prompt word into the preset code review model to obtain the model review result of the target project;
[0017] The first sending module is used to determine the corresponding architect user terminal according to the code language information, and send the model review result to the architect user terminal so that the architect user terminal can review the model review result and obtain the target review result.
[0018] The fourth aspect of the present invention application provides a project code development device, including a construction module, a review module and an update module; wherein:
[0019] The construction module is used to create a target project and construct a project flow of the target project; the project flow includes one or more code review nodes, and the code review nodes are used to execute the code review method;
[0020] The review module is used for the code review node to perform the code review method to obtain a target review result;
[0021] The updating module is used to update the project process when the target review result is approved.
[0022] The fifth aspect of the present application provides a terminal device, including a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation of the code review method or the operation of the project code development method. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 : A flow chart of the first embodiment of the code review method provided in the present application.
[0024] Figure 2 : A flow chart of a second embodiment of the code review method provided in the present application.
[0025] Figure 3 : Another flow chart of the second embodiment of the code review method provided in the present application.
[0026] Figure 4: A flow chart of the first embodiment of the project code development method provided by the present invention application.
[0027] Figure 5 : A structural diagram of the first embodiment of the code review device provided in the present application.
[0028] Figure 6 : A schematic structural diagram of the first embodiment of the project code development device provided in the present invention application.
[0029] Figure 7 : A schematic structural diagram of the first embodiment of the terminal device provided in the present invention application. DETAILED DESCRIPTION
[0030] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0031] Embodiment 1
[0032] Please refer to Figure 1 , Figure 1 A flowchart of the first embodiment of the code review method provided by the present invention application. The code review method described in the present application can be applied to computer devices, including but not limited to smart phones, laptops, tablet computers, desktop computers, and physical servers and cloud servers connected to display units.
[0033] like Figure 1 As shown, the code review method described in this embodiment includes steps S101 to S103; wherein,
[0034] Step S101, when a code change event is triggered, a code configuration file of a target project is obtained.
[0035] In this step, the code change event is based on a preset mechanism to determine the event that the code has changed compared to the previous moment or the previous period. When the code change event is triggered, the code configuration file of the target project is obtained.
[0036] The code configuration file is uploaded by the development user of the target project. Specifically, when the above-mentioned development user develops or modifies the code of the target project, the developed or modified code can be made into a code configuration file (such as a .gitlab-ci.yml file) according to the specification, and the code configuration file is pushed from the local to the remote data warehouse (such as Github), so that the device applying the code review method described in this embodiment can obtain the above code configuration file.
[0037] In this step, the code configuration file includes model prompt words, code change content and code language information.
[0038] The code language information mainly refers to the language type of the target project, including but not limited to Java, H5, JavaScript, iOS, Android, Python, etc. The code language information is used in step S102 to determine the preset code review model of the corresponding language.
[0039] When the corresponding preset code review model is determined, the model's operation process can be guided by the model prompt to review the code change content.
[0040] Optionally, in some embodiments, the code change content may be content modified by developers; in other embodiments, the code change content may be content of code changes between the latest version of a preset code branch and the previous version, which may be obtained through, for example, the git diff command.
[0041] Step S102, determining a corresponding preset code review model according to the code language information, and inputting the code change content and the model prompt word into the preset code review model to obtain a model review result of the target project.
[0042] In this step, the code language information mainly refers to the language type of the target project, including but not limited to Java, H5, JavaScript, iOS, Android, Python, etc. When determining the language type of the target project, you can select the corresponding preset code review model.
[0043] Exemplarily, in some embodiments, each preset code review model may correspond to one or more language types, such as Java language may correspond to the back-end code review model, H5 language or JavaScript language may correspond to the front-end code review model, iOS or Android language may correspond to the mobile terminal code review model, and Python language may correspond to the data analysis code model, etc. In other embodiments, each language type may correspond to a preset code review model alone, such as Java language may correspond to the Java code review model, H5 language may correspond to the H5 code review model, JavaScript language may correspond to the JavaScript code review model, iOS language may correspond to the iOS code review model, Android language may correspond to the Android code review model, and Python language may correspond to the Python code model, etc. The correspondence between the language type and the preset code review model may be determined according to the requirements of the specific application scenario. The process of determining the corresponding preset code review model according to the code language information and matching the two as described in step S102 may be implemented by a rule engine.
[0044] In step S102, the code change content and model prompt words are input into the preset code language model. The model prompt words (prompt) can be described in natural language, which guides the preset code language model. For example, it can be "As a mobile terminal architect, please review the following code...", etc. The model prompt words are essentially control instructions of the preset code language model, which can help the model understand the user's requirements, and then convert the input into the expected output results according to the requirements. Then, the preset code language model obtains the output result according to the model prompt words and the code change content, and determines the output result as the model review result of the target project.
[0045] Step S103, determining the corresponding architect user terminal according to the code language information, and sending the model review result to the architect user terminal, so that the architect user terminal can review the model review result and obtain the target review result.
[0046] In this step, the code language information includes the language type of the target project, including but not limited to Java, H5, JavaScript, iOS, Android, and Python. In this embodiment, the architect user terminal includes but is not limited to back-end architects, front-end architects, mobile architects, and data analysis architects. Each language type can correspond to one or more architects. For example, the Java language can correspond to one or more Java architects or back-end architects. This embodiment determines the corresponding architect user terminal and the preset code language model through the code language information, which can save the step of manually identifying the language type, thereby reducing the workload and saving manpower and material resources.
[0047] The model review result is sent to the corresponding architect user end, and the architect user end can further review or adjust the model review result to obtain the target review result of the target project. The conclusion of the target review result can be passed or failed, and the architect user's comments and review opinions can be attached.
[0048] In an embodiment of the present application, the architect user terminal may be a computer device, including but not limited to devices such as a smart phone, a laptop computer, a tablet computer, and a desktop computer.
[0049] In implementing the embodiment of the present application, when a code change event is triggered, a code configuration file is obtained, the code configuration file includes a model prompt word, code change content and code language information; the corresponding preset code review model is determined according to the code language information, and there is no need to manually identify the language type of the code and select the architect to review, which can save a certain amount of workload and time; the code change content and model prompt word are input into the preset code review model to obtain the model review result, and after determining the corresponding architect user terminal according to the code language information, the model review result is sent to the architect user terminal for further review, which provides a reference for the architect user's review work, reduces the time spent by the architect user on code review work, and can effectively improve the overall review efficiency and quality of the code review process.
[0050] exist Figure 1 Based on the embodiment shown, Figure 2 A flowchart of step S101 of the second embodiment of the code review method of the present invention is provided. Figure 3 This is another flow chart of the second embodiment of the code review method applied by the present invention. Figure 1 The same steps will not be repeated here. Figure 2 As shown, step S101 includes steps S201 to S203; wherein,
[0051] Step S201, monitoring a preset code branch in a data warehouse.
[0052] Step S202: When the preset code branch update is detected, determine to trigger the code change event.
[0053] Step S203: acquiring the code configuration file according to the updated preset code branch.
[0054] In this embodiment, the preset code branch is updated by the development user. When modifying or developing the code of the target project, the development user can push the result of the code change to a remote data warehouse and submit it to a specific branch, such as a test branch or a master branch, merge the code change content into the branch, and obtain the updated preset code branch.
[0055] This embodiment monitors the preset code branch to determine that the code change event is triggered, and obtains the code configuration file according to the changed preset code branch through a message hook or the like.
[0056] In some preferred implementations, the target review result includes the review conclusion of the target project. After the architect user terminal reviews the model review result and obtains the target review result, the code review method further includes: sending the review conclusion to the development user terminal through a preset application. The preset application includes but is not limited to email, office software, enterprise platform, and mobile terminal program.
[0057] When the target audit results are obtained, the review content (such as the review conclusions and the comments of the architect user) can be sent to the platform corresponding to the business process management (BPM) within the enterprise, and the above-mentioned target audit results can be obtained by monitoring the message queue (MQ), and sent to the corresponding development user end through the above-mentioned email, office software, enterprise platform and / or mobile program and other applications.
[0058] In some implementations, such as Figure 3 As shown, the preset code review model includes a code specification knowledge base and a code format knowledge base, and the code specification knowledge base and the code format knowledge base can be local knowledge bases. Step S102 specifically includes: the code change content and the model prompt words are input into the preset code review model, so that the preset code review model uses the code specification knowledge base and the code format knowledge base to review the code change content; based on the output of the preset code review model, the code specification review content and the code format review content are obtained, and the code specification review content and the code format review content are determined as the model review result.
[0059] In implementing this implementation method, the preset code review model utilizes the code specification knowledge base and the code format knowledge base to review the code change content, and obtains the code specification review content and the code format review content based on the output of the preset code review model. This can save the time and energy spent by architect users on code specification review and code format review, further reduce the workload of architects, and in addition, the efficiency and quality of code review of the target project are further improved.
[0060] As a preferred solution, step S103 of sending the model review results to the architect user terminal includes: packaging the model review results to obtain a data packet; initiating a business management process, and when the business management process is approved, sending the data packet to the architect user terminal.
[0061] When a data package is obtained, the model review content or opinions in the data package can be sent to the platform corresponding to the business process management (BPM) within the enterprise. In the above business management process, a code review sub-process is initiated, and the corresponding architect user end is matched from the architecture group according to the target project information, and the data package is sent to the corresponding architect user end for review.
[0062] Furthermore, when the business management process is approved, the data packet is sent to the architect user terminal, including: monitoring the message queue of the business management process, and when it is monitored that the business management process is approved, sending the data packet to the architect user terminal through a preset application.
[0063] Exemplarily, this embodiment can obtain the above-mentioned data packet by monitoring the message queue (MQ for short), and send the data packet to the architect user terminal through the above-mentioned email, office software, enterprise platform and / or mobile program and other applications, prompting the architect user terminal to further review it. The architect user terminal does not need to manually confirm or contact the developer to understand whether there are any code changes, thereby further shortening the code development cycle of the target project.
[0064] exist Figure 1 Based on the embodiment shown, the present invention also provides a project code development method. Figure 4 A flowchart of a first embodiment of a project code development method according to the present invention is shown.
[0065] The project code development method described in the present application can be applied to computer devices, including but not limited to smart phones, laptops, tablet computers, desktop computers, and physical servers and cloud servers connected to display units.
[0066] Figure 4 The illustrated embodiment includes steps S401 to S403, which are described in detail as follows:
[0067] Step S401, create a target project and construct a project flow of the target project; the project flow includes one or more code review nodes, and the code review nodes are used to execute the code review method described in any one of the above implementation methods or examples.
[0068] Step S402: obtaining a target review result based on the execution result of the code review method by the code review node.
[0069] Step S403, when the target review result is approved, the project process is updated.
[0070] In this embodiment, while creating the target project, you can submit the .gitlab-ci.yml file (code configuration file) in accordance with the specifications to build the project process of the target project. The project process can be the above-mentioned business management process or the code project process. In the project process, one or more code review nodes can be included, and each of the code review nodes executes the code review method. After the code review node executes the code review method, the execution result is obtained, and then the target review result is obtained. The target review result includes the review conclusion of the architect user. When the review conclusion is that the review is passed, the code change content can be used to update the project process of the target project, and the progress of the target project is effectively promoted while ensuring that the code is efficiently reviewed.
[0071] In the implementation of this embodiment, when developing the code of the target project, the target project is created and its project process is constructed. The process includes one or more code review nodes. The development or change of the code in the project process is reviewed through the code review nodes, and the corresponding preset code review model is determined according to the code language information during the code review. There is no need to manually identify the language type of the code and select the architect to review, which can effectively save manpower and material resources in the target project code development process; and after the model is reviewed, the model review result is sent to the architect user end for further review, which can provide a reference for the code review work of the architect of the target project and reduce the time spent by the architect on the code review work; in addition, the target review result is obtained based on the execution result of the code review node, and the project process is updated when the result is approved, which can effectively reduce the time spent on the code review link of the target project, shorten the project cycle and improve the code development efficiency of the project.
[0072] exist Figure 1 Based on the embodiment shown, Figure 5 A schematic diagram of the structure of a first embodiment of a code review device 500 of the present invention is provided. The code review device 500 comprises an acquisition module 501, a review module 502 and a first sending module 503;
[0073] The acquisition module 501 is used to acquire a code configuration file of a target project when a code change event is triggered, wherein the code configuration file includes model prompt words, code change content and code language information;
[0074] The review module 502 is used to determine the corresponding preset code review model according to the code language information, and input the code change content and the model prompt word into the preset code review model to obtain the model review result of the target project;
[0075] The first sending module 503 is used to determine the corresponding architect user terminal according to the code language information, and send the model review result to the architect user terminal so that the architect user terminal can review the model review result and obtain the target review result.
[0076] In some preferred implementations, when a code change event is triggered, the acquisition module 501 acquires a code configuration file of a target project, including:
[0077] The acquisition module 501 monitors the preset code branches in the data warehouse;
[0078] When monitoring the update of the preset code branch, determining to trigger the code change event; wherein the preset code branch is updated by the development user end;
[0079] According to the updated preset code branch, the code configuration file is obtained
[0080] In some preferred implementations, the preset code branch is updated by the development user end, including:
[0081] The development client pushes the local code changes to the data warehouse; merges the local code changes into the preset code branch to obtain the updated preset code branch.
[0082] In some preferred embodiments, the target audit result includes the review conclusion of the target project;
[0083] After the architect user terminal reviews the model review result and obtains the target review result, the code review device 500 also includes a second sending module, which is used to send the review conclusion to the development user terminal through a preset application.
[0084] In some preferred implementations, the preset code review model includes a code specification knowledge base and a code format knowledge base;
[0085] The review module 502 inputs the code change content and the model prompt words into the preset code review model to obtain the model review result of the target project, including:
[0086] The review module 502 inputs the code change content and the model prompt word into the preset code review model, so that the preset code review model reviews the code change content by using the code specification knowledge base and the code format knowledge base;
[0087] Based on the output of the preset code review model, code standard review content and code format review content are obtained, and the code standard review content and code format review content are determined as the model review result.
[0088] In some preferred implementations, the first sending module 503 sends the model review result to the architect user terminal, including:
[0089] The first sending module 503 packages the model review result to obtain a data packet;
[0090] Initiate a business management process, and when the business management process is approved, send the data packet to the architect user terminal.
[0091] In some preferred implementations, when the business management process is approved, the first sending module 503 sends the data packet to the architect user terminal, including:
[0092] The first sending module 503 monitors the message queue of the business management process, and when it is monitored that the business management process is approved, sends the data packet to the architect user terminal through a preset application.
[0093] exist Figure 4 Based on the embodiment shown, Figure 6 A schematic structural diagram of a first embodiment of a project code development apparatus 600 is provided. Figure 6 The project code development device 600 includes a construction module 601, a review module 602 and an update module 603; wherein,
[0094] The construction module 601 is used to create a target project and construct a project flow of the target project; the project flow includes one or more code review nodes, and the code review node is used to execute the code review method described in any one of the above implementation methods or embodiments;
[0095] The review module 602 is used for the code review node to perform the code review method to obtain a target review result;
[0096] The updating module 603 is used to update the project process when the target review result is approved.
[0097] In addition, the present invention application also provides a terminal device, including a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation of the code review method or the operation of the project code development method.
[0098] Figure 7 A schematic diagram of the structure of an embodiment of a terminal device of the present invention is shown, and the specific embodiment of the present invention does not limit the specific implementation of the terminal device.
[0099] like Figure 7 As shown, the terminal device may include: a processor (processor) 702 , a communication interface (Communications Interface) 704 , a memory (memory) 706 , and a communication bus 708 .
[0100] The processor 702, the communication interface 704, and the memory 706 communicate with each other via a communication bus 708. The communication interface 704 is used to communicate with other devices such as a client or other server network elements. The processor 702 is used to execute a program 710, which can specifically execute the relevant steps in the above-mentioned embodiments of the code review method or the project code development method.
[0101] Specifically, the program 710 may include program code including computer executable instructions.
[0102] The processor 702 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiment of the present invention. The one or more processors included in the terminal device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0103] The memory 706 is used to store the program 710. The memory 706 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0104] The specific embodiments described above further illustrate the purpose, technical solutions and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. It is particularly pointed out that for those skilled in the art, any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of protection of the present invention.
Claims
1. A code review method, characterized in that: include: When a code change event is triggered, a code configuration file of a target project is obtained, wherein the code configuration file includes model prompt words, code change content, and code language information; Determine a corresponding preset code review model according to the code language information, and input the code change content and the model prompt word into the preset code review model to obtain a model review result of the target project; The corresponding architect user terminal is determined according to the code language information, and the model review result is sent to the architect user terminal so that the architect user terminal can review the model review result and obtain the target review result.
2. A code review method as claimed in claim 1, characterized in that: When a code change event is triggered, the code configuration file of the target project is obtained, including: Monitor the preset code branches in the data warehouse; When monitoring the update of the preset code branch, determining to trigger the code change event; wherein the preset code branch is updated by the development user end; The code configuration file is obtained according to the updated preset code branch.
3. A code review method as claimed in claim 2, characterized in that: The preset code branch is updated by the development user end, including: The development client pushes the local code changes to the data warehouse; merges the local code changes into the preset code branch to obtain the updated preset code branch.
4. A code review method as claimed in claim 2, characterized in that: The target audit results include the review conclusions of the target projects; After the architect user terminal reviews the model review result and obtains the target review result, the code review method further includes: sending the review conclusion to the development user terminal through a preset application.
5. A code review method as claimed in claim 1, characterized in that: The preset code review model includes a code specification knowledge base and a code format knowledge base; The step of inputting the code change content and the model prompt word into the preset code review model to obtain the model review result of the target project includes: Inputting the code change content and the model prompt word into the preset code review model, so that the preset code review model reviews the code change content by using the code specification knowledge base and the code format knowledge base; Based on the output of the preset code review model, code standard review content and code format review content are obtained, and the code standard review content and code format review content are determined as the model review result.
6. A code review method as claimed in claim 1, characterized in that: The sending the model review result to the architect user terminal includes: Packaging the model review results to obtain a data package; Initiate a business management process, and when the business management process is approved, send the data packet to the architect user terminal.
7. A code review method as claimed in claim 6, characterized in that: When the business management process is approved, sending the data packet to the architect user terminal includes: The message queue of the business management process is monitored, and when it is monitored that the business management process is approved, the data packet is sent to the architect user terminal through a preset application.
8. A project code development method, characterized in that: include: Create a target project and build a project flow for the target project; The project process includes one or more code review nodes, and the code review nodes are used to execute the code review method according to any one of claims 1 to 7; Obtaining a target review result based on the execution result of the code review method by the code review node; When the target review result is approved, the project process is updated.
9. A code review device, characterized in that: It includes an acquisition module, a review module and a first sending module; wherein, The acquisition module is used to acquire a code configuration file of a target project when a code change event is triggered, wherein the code configuration file includes model prompt words, code change content, and code language information; The review module is used to determine the corresponding preset code review model according to the code language information, and input the code change content and the model prompt word into the preset code review model to obtain the model review result of the target project; The first sending module is used to determine the corresponding architect user terminal according to the code language information, and send the model review result to the architect user terminal so that the architect user terminal can review the model review result and obtain the target review result.
10. A terminal device, characterized in that: It includes a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform the operation of the code review method as described in any one of claims 1 to 7, or the operation of the project code development method as described in claim 8.