check-best-practices

You can audit code changes by running a best practices check on your local branch. This systematically analyzes your code diff against defined documentation to identify violations, correctness bugs, and security issues, providing a detailed report with actionable fixes.

An automated best practices check identifies violations in added lines of code, specifically flagging correctness bugs, security issues, banned APIs, and architectural deviations across various file types like C++, frontend, and mobile platforms.

Yes, best practices auditing supports both Android and iOS mobile platforms. It applies categorized rules based on file types, systematically checking mobile code alongside C++, frontend, build system, and documentation files.

You can check your local branch diff by running an auditing script against best practice documents. It systematically evaluates added lines of code to detect banned APIs and architectural deviations, generating a clear pass or fail status report.

The best way to ensure C++ code compliance is to run an automated best practices audit on your local branch. This evaluates your C++ files against established guidelines, catching security issues and correctness bugs before the review process.

Yes, you can use documentation checks alongside build system audits. The auditing process systematically analyzes both build system and documentation files, applying categorized rules to ensure comprehensive compliance across all project areas.