review-validate

You validate code review documents by running a validation check on review.md files to confirm required frontmatter fields like name and description, along with mandatory sections including Context, Iterations, Verdict, and Status, are present and correctly named.

The required sections in a standard code review document are Context, Iterations, Verdict, and Status. Additionally, the document must include frontmatter with both name and description fields to ensure proper structure and traceability.

Yes, you can run pre-commit validation on all code review markdown files at once by executing a bulk validation command with an --all flag, which checks every review.md file against the required frontmatter and section standards.

Yes, code review linting checks for a clear status field to verify whether it is marked as OPEN or RESOLVED. This ensures the review document maintains a clear and actionable verdict alongside its required sections.

Your review.md fails validation when it is missing required frontmatter fields like name or description, lacks mandatory sections such as Context, Iterations, Verdict, or Status, or contains misnamed structural elements that violate the standard.