coding-guideline-review

To review Rust coding guideline PRs, the skill analyzes file placement, validates mandatory frontmatter fields, verifies FLS linkage, checks citations against authoritative Rust documentation, and confirms CI status across workflows to generate transparent review artifacts.

Safety-critical Rust coding guidelines require validating mandatory frontmatter fields, verifying FLS linkage, mapping claims to authoritative sources, checking file placement, and confirming CI validation status to prevent regressions and maintain correctness.

Validating frontmatter fields and citations involves enforcing required field values, mapping claims to authoritative Rust documentation sources, and verifying cross-guideline consistency to ensure repository style rules are met.

Yes, the PR review tool verifies CI status across workflows and checks file placement to ensure coding guideline PRs align with repository validation checks and style rules for safety-critical Rust software.

You generate review artifacts by submitting the coding guideline PR URL, which triggers a standardized review workflow that produces a summary and inline comments based on comprehensive field validation and citation mapping.

The best way to enforce cross-guideline consistency is applying standardized PR review workflows that validate frontmatter, map citations to Rust documentation, and verify FLS references to prevent guideline regressions.