quality-review

To review code changes for Clean Architecture and KMP safety, provide the recent code diff to analyze architectural boundaries, platform compatibility, and structural compliance. The evaluation checks whether changes adhere to established project standards.

A security assessment for pull requests checks for hardcoded secrets, unauthorized access paths, and potential data leaks. It analyzes security configurations within the code changes to identify and minimize vulnerabilities before integration.

To automate test coverage and quality checks for a pull request, submit the change scope to examine test completeness, assertions, and overall code robustness. This evaluates whether the modifications meet minimum testing requirements.

This quality assurance review is specifically configured for the Strakk project, analyzing code changes against its dedicated Clean Architecture, KMP safety, and security standards. It may not yield accurate results for unrelated project architectures.

The best way to minimize security vulnerabilities in KMP code changes is to run an automated review focusing on security configuration, unauthorized access, and data leak detection. This identifies potential risks within architectural boundaries.

You do not need to provide the full codebase to check architectural boundaries and platform compatibility. Providing the recent code diff or specific change scope is sufficient to evaluate conformity with project standards.