mo-needs-to-review?

To assess uncommitted code changes for production risk, run static checks on your git workspace to evaluate encryption practices, backward compatibility, migrations, and environment variables, returning a clear decision on whether a senior review is required.

Automated risk assessment for code review statically analyzes your working tree to detect production-risk changes, unsafe logging, or security gaps. You need it before opening a PR when changes touch core components, database migrations, or introduce new environment variables.

To check if database migrations or new environment variables require a senior engineer review, run static checks on the current work tree to evaluate migration status and configuration changes, escalating to Mo when risk is detected.

Yes, this risk assessment works with backend services and feature evolution changes. It applies static checks aligned with backward compatibility, test results, and security practices to determine if changes require a second manual confirmation.

The static checks applied to uncommitted changes include verifying encryption and security best practices, assessing backward compatibility, checking migration status, validating new environment variables, and ensuring the avoidance of unsafe logging.

You should escalate code changes to Mo for a second manual confirmation when the static checks detect risk in production-impacting areas like security practices, backward compatibility, database migrations, or test results within your uncommitted working tree.