Dynamic review of software updates after pull requests

A system for rule-based review of software code changes, the system comprising:

• one or more memories;
• and
• one or more processors, communicatively coupled to the one or more memories, configured to:
• receive, from a software repository, a difference file indicating at least one change, to software code, that was submitted to the software repository;
• parse the difference file to determine one or more files, associated with the software code, affected by the at least one change,
• wherein parsing the difference file to determine the one or more files comprises determining a change in one or more filenames identified in the software code based on association with a file extension;
• select a rule dictionary that identifies one or more rules associated with software code changes;
• apply the one or more rules to generate one or more software review checklist items, wherein at least two different rule dictionaries cause generation of different software review checklist items;
• output a graphical user interface (GUI) that provides the one or more software review checklist items for display;
• receive, based on input from a user and using the GUI, confirmation of the at least one change;
• and
• commit the at least one change to the software repository based on the confirmation of the at least one change.

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:
• receive, from a software repository, an application programming interface (API) call that was triggered by at least one change, to software code, that was submitted to the software repository;
• receive, from the software repository, a difference file indicating the at least one change;
• schedule, using a load balancer, execution of a parser to apply to the difference file;
• parse the difference file, using the parser, to determine one or more files, of the software code, affected by the at least one change,
• wherein the one or more instructions, that cause the one or more processors to parse the difference file to determine the one or more files, cause the one or more processors to determine a change in one or more filenames identified in the software code based on association with a file extension;
• schedule, using the load balancer, execution of a checklist generator to apply to the parsed difference file;
• apply one or more rules, from a rules dictionary and using the checklist generator, to generate one or more software review checklist items, wherein at least two different rule dictionaries cause generation of different software review checklist items;
• and
• output, to the software repository, the one or more software review checklist items for display.