arkweb-committer-review

Reviewing ArkWeb code changes against design documents requires validating API signatures, naming, and file structures against the original design. This process flags missing or extra behavior to ensure strict design-to-code conformance before submission.

A committer-level code review for ArkWeb covers correctness, architecture, security vulnerabilities, performance hazards, thread safety, compatibility regressions, and testability. It enforces ArkWeb layer compliance from API to framework to kernel.

To generate a structured code review report for ArkWeb, input the design document path and generated code directory into a review tool. It outputs a Markdown report containing severe issues, improvement suggestions, best practices, and a pass or fail conclusion.

Yes, ArkWeb code review checks Chromium coding style expectations and verifies ArkWeb layer compliance across API, framework, and kernel layers. This ensures architectural integrity and aligns implementations with established coding standards.

Yes, you can include code analysis results when reviewing ArkWeb implementations by providing an optional code analysis result path alongside the design document and code directory. This enriches the risk-focused validation for security and performance.

Your ArkWeb code may fail design conformance checks if the implementation has mismatches in APIs, signatures, naming, or file structures compared to the design documents. The review process specifically flags these missing or extra behaviors.