code-review

To perform a code review on OpenWOP implementation artifacts, run the code-review skill on your codebase. It executes 8 mandatory checks, detects banned patterns, and analyzes code against categories like wire-shape stability and replay determinism to ensure quality and compliance.

A code analysis for OpenWOP compliance checks for banned patterns, wire-shape stability, security invariants, replay determinism, and schema discipline. It executes 8 mandatory checks and provides a detailed report of findings categorized by severity.

Yes, you can use automated checks to stop a code review if banned patterns are found. The process executes 8 mandatory checks and halts the review immediately upon detecting any banned patterns in your OpenWOP spec artifacts.

The best way to ensure security invariants and replay determinism is to run a code analysis against these specific review categories. This process analyzes your code and provides a detailed report of findings categorized by severity.

Yes, you need OpenWOP implementation artifacts and spec artifacts to run a quality assurance check. The review process analyzes these specific artifacts to ensure adherence to strict quality and compliance standards.

Your code review report shows findings categorized by severity because the analysis evaluates your code against various categories like schema discipline and wire-shape stability. This detailed output format highlights the compliance issues found during the mandatory checks.