skywatch-reviewing-osprey-rules

Validate Osprey SML rules by running an automated three-layer verification process that checks syntax, logic, and project-specific conventions to prevent runtime type errors and dead code before merging.

Automating code review for ATProto security rules requires a multi-layered validation process that enforces SML structural and naming standards, categorizing issues by severity to streamline pull request reviews.

Yes, you need the osprey-cli tool to check SML compliance, as the validation process executes CLI validation alongside proactive logic analysis and convention enforcement for your rule sets.

Enforce naming conventions for Osprey SML rules by applying an automated convention check within your pull request workflow, which generates a structured report flagging violations as Critical, Important, or Minor.

The three-layer SML validation report includes categorized issues by severity—Critical, Important, and Minor—covering CLI validation, logic analysis, and convention enforcement to streamline the review process.